"WCF Technology Insider" Translation 3:1th Part _ 1th Chapter _ Blue Moon: Universal demand and general concept

1th Chapter: Blue Moon

Business and market new functional requirements for software systems look greedy. I once heard a product manager in a product launch after the river I said: "This product can do anything the customer wants to do; the next version has nothing to design. We'll all be home. " When the release date arrives, the most likely thing you'll hear is, "No, this version is not going to do this, and we might be able to add this feature after the next version." "In the software world, these functional requirements are accidentally lumped together and seem to be a common requirement in the distance." Sometimes, one of the common requirements creates a new generic concept that carries the promise of satisfying this common demand. Once the time comes, interest in new technologies will drive a new technology that allows developers to apply the concept to their applications, thus satisfying that common need. Every time this is a once-in-a-century, universal demand, common concepts and the new technology that comes with it are so huge and important that we have to rethink the design of the software. I'm not sure if you've noticed this, but the Microsoft WCF release has a big impact. It's time for us to rethink how to design and construct distributed applications.

Note: The Moon is Blue, the moon is bluish: this will require an understanding of the cultural background of the western countries, a once-in-a-lifetime event. It is usually very rare to have a huge impact, with the doubts of the times, such as the proposed theory of relativity. Human first time on the moon and so on. The author uses this title to emphasize the far-reaching significance of WCF's emergence. Detailed reference to the end of the article interpretation.

General needs:

For the most part, businesses are no longer looking for magical applications that can solve all their computing problems. Over time, many software vendors, such as the Enterprise Resource Planning (ERP) and middleware vendors, have successfully sold the system in varying degrees. Business, however, has made so many demands that no product from that software vendor can meet all of the requirements. In addition, as business develops, they often need to develop their own infrastructure and processes to adapt to growth. Software can run on a 100-person scale, and then not necessarily work at 1000 employees. The problem is more complicated when considering mergers and acquisitions. Migrating an acquired company to use the corporate software system is very painful, tedious and costly.

The result is that most of the company's computing architecture includes an application hybrid system that meets both departmental and enterprise-level requirements. This mixture is often referred to as the Non-mainstream architecture. Most likely, these systems are developed by internal or external vendors to address specific business issues, and each system often manages isolated information. Occasionally these non-mainstream architectures are also standardized to run on specific hardware, operating systems, and platforms, but such standardization is often difficult to generalize. More often, computing systems within these enterprises are composed of independent, isolated applications that run on different hardware, operating systems, and platforms to improve business (hopefully). If you see the picture on the right, you may remember the painting of M. Escher.

From a business standpoint, applications rarely exist independently, just as they are closely linked and help businesses operate more efficiently in some form and shape. As a result, some people are inevitably required to cut costs, increase sales, or a disguised requirement: "I want to know something about system B in application system A." "The change of demand is the connection.

There are clearly two ways to connect: application-Application and application-enterprise. Only applications-applications are connected to two applications, such as accounts receivable systems and transportation systems. An application-an example of an enterprise is that the route wants to release every time a plane takes off and lands information to all concerned about its application system. This information will profoundly affect businesses, including operations, employee scheduling, and quality assurance. The need for people, markets, and businesses to connect to their systems is now very common. Whether you're working for a software vendor or a company's in-house IT department, you probably have seen the need for interconnected systems. If this is the first time you've heard about it, just read some of the comments from mainstream software companies and write down their announcements about the future, such as software products and services. With almost no exceptions, you will at least hear and see the words about integration, interconnection, and interoperability. These all imply the connection. In short, the universal need to connect to the newer.