SOA-related concept analysis

The    1,soa----an architectural guideline centred on describing and exposing it assets to (remote) services. These services can then be loosely coupled as part of the high-level business process, providing business agility in the face of it heterogeneity. A design approach that aims to improve it adaptability and effectiveness by reusing application-neutral services. SOA is an enterprise-integrated solution that leverages Web services and the business Process Execution language (Business process Execution language,bpel). These technologies provide an open, standards-based integration that provides interoperability through the combination of messaging technologies and XML and various web services standards. Once the Web service interface is developed, you can use BPEL to define and orchestrate business transactions, ultimately transforming legacy systems into new modern information systems.     2, (remote) service, refers to the ability to provide remote invocation of components. Provides a feature. can provide services for remote clients. Ejb,jms,corba,com,web service, such as remote call mechanism, is said here services.   3,web Services is the raw material for SOA. It addresses compatibility issues with other remote invocation mechanisms. It has nothing to do with any language or platform. Almost all remote invocation mechanisms can generate Web Services. WEB Services is the world language for remote service. Although SOA may not necessarily be Web services, the proposed SOA concept and today's buzz are largely due to the global language of Web services, a remote service that eliminates the barriers to remote reuse of enterprise IT assets.   4,ESB (Enterprise services Bus) CORBA has servers, publishing and managing CORBA remote services; COM component industry has server DCOM, publishing and managing CORBA remote services; JMS, EJB also has server Java-EE, publishing and managing remote services under the Java EE platform. WEB services can be published by various middleware servers. However, there are no servers to manage them. For example, the Java server does not have the ability to manage Web services. ESB (Enterprise services Bus) Enterprise service buses are the middleware servers for such a Web services. It publishes and manages all Web Services, just as the EJB container uses Jndi to publish and manage all remote EJBS. An ESB server is the place where Web services are stored and managed.is where SOA gets Web services. This also helps SOA developers manage, find, and reuse Web Services.   5,bpel (Business process Execution Language) Business Program execution language. There are also called BPEL4WS or BPELWS, which means that the business program that uses Web services executes the language. The meaning is all the same. This is an extension of the workflow language/Business Program Management language, which is a business program that can use Web services to service business programs. XPDL is a business programming language specification. JBPM provides an extended JPDL language. It uses a UML-like activity diagram. You can use Business program variables, scripting languages, and Actionhandler implementation classes. Because it's a business program engine that uses only Java-Pojo classes. So you can use some of the Java features. In fact, we can also use Pojo to represent Web services and indirectly invoke Web services. However, because it is a JPDL language and relies on Java, the Business program definition cannot be used directly by different language platforms. Although BPEL is just an extension of the Business Program Management engine, it uses only Web services, and thus has some special requirements. 1, it does not use any particular programming language. WEB Services is a descriptive language that is detached from a specific language implementation. So, in BPEL, we can't use any particular language. 2, in Jpdl, we can delegate Web services to execute business logic in Actionhandler. However, we can use Java syntax in Actionhandler to perform specific functions. In BPEL, the only thing we can use is the existing Web Services, so we have to provide some syntax for the programming language to help us complete the business process using only the BPEL syntax. Note, however, that we may ultimately not be able to build Bpel from a specific language.     has now put forward BPEL, which bpelj this Java extension.