SOA Anxiety Disorder

Gartner presented the SOA concept in 1996.

Gartner has also presented two well-known concepts:

ERP, enterprise resource planning. To organize enterprises ' people, wealth, goods and information in the perspective of enterprise resources. This concept is produced in the era of production MRP, call the upstream and downstream of the enterprise into the overall strategic consideration. Because society has become the industrial chain, from raw materials to production to logistics to sales to after-sales service, each link has an impact on production enterprises. Production has become not the first important, the era of supply is over. Into the era of marketing channels.

CRM, customer relationship management. Re-organize the people, business, process and information of the enterprise in terms of customer service. This concept on the basis of ERP, the vision from the upstream supply chain and production enterprises to the customer terminal. The end of the production era, marketing sales era is also near the end, regardless of customer experience, not with the customer interaction, blindly production and marketing, it is impossible to win.

(From what perspective to organize resources and processes, rather like the technology industry-oriented process, object-oriented, component-oriented, now service-oriented)

In such a big background, Web2.0 is also adapt to the concept of production, Word-of-mouth marketing, accurate audience, circle, instant Messaging, SMS, blog, a variety of interactive tools to adapt to the times.

Both ERP and CRM are the product of application level.

This application, in the information aspects how to fall.

The SOA concept then appears.

The United States in the 1996, the Internet has been very developed. But the Internet technology has not followed. Enterprises are still closed in their own information world. Although there are CORBA, COM +, RMI/EJB These technical models are supported, but to the Internet to provide information services to the public, rather than upstream and downstream partners to provide information services, CORBA, COM +, RIM/EJB still in the penetration of firewalls and universal data format transmission still have problems, All three systems have their own communication protocols and data transmission protocols, which ordinary consumers cannot participate in.

2000, XML was generated. Random HTTP based soap, WSDL, UDDI Generation, WebService as an internet-based universal technology based on the development of data communication protocol and Transmission Access Protocol system.

But webservice only defines data communication and transmission access based on universal Internet technology. is equivalent to the underlying pathway. But based on the above application, there is still no specification. It is the equivalent of the road, but on this road what kind of car running the most smooth, there is no such specification. (Of course you don't have to spec yourself to build your own car, and then there's a problem when interacting with a car that has a uniform size.) This description is also to answer the question posed by a considerable part of the people: since we have webservice, why do we have to sca/sdo? ）

SOA is the thing to do.

But, SOA, the industry bosses are too anxious. Just like in. COM tide, every enterprise is eager to affirm that we are a. com company. So, this market confuses a variety of audio-visual.

The workflow, doing OA, doing business base platform, doing components, doing middleware, doing EAI, all claim that they are already SOA. Some say SOA is for business agility (you can adjust your system flexibly to adapt to rapidly changing business competition.) Here's a quote: SOA by breaking down traditional application modules into smaller artifacts and using them as reusable Web services, CIOs can generate the most fit systems by selecting and arranging the artifacts they need. This is similar to how we used to do the Windows DNA architecture. But no one has said that the Windows DNA architecture is an SOA architecture when SOA has been proposed. The reason why this noun is not popular. , some say SOA is for system integration, some say SOA is enterprise bus, some say SOA is a kind of business analysis design idea, some say SOA is technology architecture model, some say SOA is similar to the role of UML, can make business designers and technical designers have common language, Some people say that SOA is the same concept as web2.0. It was like Microsoft was rushing to put all of its products on the phone. NET logo, the end of the people are confused about what is. NET. Until 2007, after the release of WPF, WCF, WF. NET's technology trend is to calculate the basic architecture stereotypes. SOA is very similar to. NET at the time.

Today, the SOA specification is truly the ground for SCA and SDO. The workflow specification industry has been formed, WF also conforms to the industry workflow specification, so there is no workflow specification defined in SOA. SOA, for its part, obviously does not need to be, after all, SOA is about the Business interface service level, not what graphical interface specification the service is using to allow customers to access it, and there is no need to (China Primeton this link. China Primeton is also one of the top Osoa members. If there is no UI for the interface or the programmer is required to write the UI, it is impossible for business people to have the UI to make flexible changes to business functions and processes, even with BPEL and DSL. Don't give business people any technical stuff, and don't think about DSL and UML for business people to use. So SCA and SDO are enough, and the SOA architecture is really shaping up.

But SCA and SDO were only finalized in August 2007 (although the 2005 has been drafted). So it's not known how eager to be a SOA product maker.

I read the SCA and SDO standards, I also compared to the previous CORBA I studied, I also compared to Microsoft's WCF, architectural ideas are very similar.

When Dec and IBM led the definition of CORBA, too complex, sun and Microsoft have made customized cuts, developed their own rmi/ejb and COM +. Thanks to the advent of WebService, Microsoft has immediately developed an architecture based on WebService: WCF. But the Java world has been slow to develop due to the large number of manufacturers involved in standard-setting. IBM, too, is unwilling to embarrass itself as a shadow giant in the Sun's Java world. IBM has been figuring out how to be a leader.

So the real architecture of SOA absorbs the lessons of CORBA (IBM was annoyed by the fact that CORBA did not bring up industry standards, this time to make a comeback, to learn smarter, who said elephants can't dance), and to combine WebService, Also borrowed from WCF (WCF is also in WebService based on the development of the framework, many technologies borrowed webservice technology, rather than another set of the bottom), finally produced.

The OSOA organization, which has only recently seen Sun, does not have a draft in the SCA and SDO standards that sun has submitted.

Java and. NET two platforms, closed and proprietary. What IBM needs is an industry-standard-makers. SOA this time has reached IBM's will. Whether it's Java, or. NET, or even PHP, you can provide an industry-standard service interface as long as it conforms to SCA and SDO.

Freed from the cage of language and proprietary platforms, the IBM blue giant has become a free industry god.

Why I am so focused on and trusting and understanding SOA. In fact, and my own in the software industry is very related.

I am the enterprise management software. Early in the industry there was a consensus that software could not be sold like this. We sold a set of office systems to operators, and they used our software to do services that cost more than we sell software.

So, even sell software boss Microsoft is shouting software service.

In the past is the software running inside the enterprise, an enterprise is nothing more than so many people so much data. However, once the software has been serviced and the internet has been made, it will not be worth the visit of many people.

So, how do we deal with software service, Internet.

Hundreds of millions of people visit the WebService, its architecture can not be like building the internal operation of the software architecture, you see Google, there are hundreds of thousands of PC cluster computing resources to support Internet services. We used to have the traditional enterprise internal computer room disk array and cluster architecture is not suitable for the public network, our database is not suitable for hundreds of millions of people.

So, I am particularly concerned about how we can service the software and what is the architecture of the software service.

In fact, the industry is running in one direction, whether it is Google, Yahoo, or Microsoft, or our Baidu, QQ, Grand, Ali, everyone in the software services, the direction of the Internet run. (If you're simply looking at SaaS and putting it in the past with the asp[Application service), the horizons obviously need to be higher.

Application software operation requires infrastructure. First, the basic hardware facilities, hundreds of thousands of PCs cluster how virtual file system and computing resource allocation, this is the cloud computing to solve the problem. Now cloud computing is a hot spot, Yahoo, Google, IBM, Microsoft are all in research and construction. But Microsoft has been slow (Microsoft has been insensitive to Internet computing, looking at the Internet in traditional software), so WFS didn't come out (probably not figured out as a node resource in a cluster, how to join the cluster, and cluster isomorphism, but also to meet the Personal desktop computing management).

With the hardware foundation of cloud computing, the data Access Software Foundation is also needed. With Distributed File system, file access should be no problem, but the access of relational data, which is now all database products are not resolved. Amazon saw the opportunity to launch the S3 service. The global Internet is a supercomputer, and S3 is the database on this computer.

And all the SOA applications, must be run in a container, otherwise, there are outside calls to these services, and the resources used in running these services are managed by WHO (many people do not understand what the container is for, do not understand the origins of the middleware, and do not understand why Java and. NET have to do containers. If you do the application, you are responsible for so many low-level distribution and release and concurrency, then you do not professional, but also tired, unstable, rather than to the system to manage the business. The container is responsible for the memory, resource allocation, dispatch, recycling, responsible for security, responsible for the transaction, responsible for concurrency, responsible for pooling. And these SOA services, must be able to upgrade at any time, you must have the software hot-swappable function. Hot OSGi Research is now in this category.

With these infrastructures, our applications must be SOA and become software services for everyone to use. The user side may be a C # write client, may be a PHP site, may be a Java Web site, may also be a flash.

Large and small companies around the world provide so many open APIs and how to invoke them. In their own language. Java. C#. Php. Javascript.

I would like to create a new language to organize these open APIs, rather than the development coding language used by such a technical programmer.

It, it would be DSL. Domain specific language. It may be higher than JavaScript, but similar to JavaScript, but less than java,c# these heavy development languages. But it must be a dynamic language. This changes the process at any time and changes the application at any time. This is business agility.

This is what I envisioned as the future SOA era computing environment.

You are still using the traditional business basic platform idea to build enterprise management software architecture.

Future SOA era, the future of the software service era, are you ready?

Postscript:
20% of enterprises in the first generation system, do not need SOA. But software product providers need to consider SOA to prevent future integration. But now there is no demand for the enterprise, and it will not pay for SOA plus points.
30% of all enterprises replace the first generation of systems and do not need SOA. But software product providers need to consider SOA to prevent future integration. But now there is no demand for the enterprise, and it will not pay for SOA plus points.
30% of companies are consolidating their own internal second-generation systems, which may require SOA, but in essence less. But software product providers need to consider SOA to prevent future integration. Customers may be paying for SOA plus points.
10% of companies are integrating their own up and down trips and need SOA.
10% of businesses are starting to provide information interaction services to end customers, just as we see the Google API, which requires SOA.

Now is the right time to focus on and write SOA? Right, because you see the ratio above, 50% of the companies have SOA requirements.
But if you are facing a customer market that is not exactly 50%, but another 50%, then advise you to continue to do the current product, SOA does not need.