|
Application software development methods in the past 40 years, has experienced many significant changes: process-oriented development, object-oriented development method, component-oriented development methodology, as well as the now popular service-oriented development method. In order to become more competitive, companies must create a business-oriented, reliable architecture of a service-oriented architecture (SOA) is used instead of the past dispersed, dedicated application platform. Therefore, SOA gradually become applicable to the design of the architecture in the form of the modern enterprise applications, the core idea is to use open standards enterprise business functions packed into standard services, such services through clear, independent interface to define Services are loosely bound, and can be invoked by emphasizing the location transparency and interoperability of communication protocols. Standards-based, loosely coupled, flexible, agile characteristics of SOA, it appears to bring a great deal of competitiveness. However, if only in the service, there is no interaction, then the presence of the service is no. Collaboration between the services are carried out by ESB to services does not directly contact the service request / response, publish / subscribe events are carried out by the ESB. Service Bus can change the message format between service providers and requestors, routing to the correct service provider, protocol conversion between service providers and service users, as well as providing security, strategy, transaction management, and other functions. SOA and software development process, one of the biggest difference is that SOA is a business-driven, and the traditional software development is driven IT. Business-driven development is driven by the business needs of software development methods, starting from business requirements analysis to promote under the design, development and testing at the demand of the business objectives. We propose a business-driven SOA development process: understanding the business needs, requirements analysis; service design and realization; assembly and deployment services. Based on the practice, the project communication service, for example, the use of the concept of SOA and ESB, the first analysis of the demand for communication services, a clear business need to meet the target. Then we can reflect the main value of the communication services, and architectural design will produce the global impact of the four typical use cases as the focus of investigation. Next, the principles and ideas of the overall design of the system, the overall system architecture and communication services design the detailed description given concrete implementation. Deployment and assembly of our services, we have chosen the open source implementation of Mule ESB. Mule open source ESB as an earlier implementation, maturity is relatively high, and active development community; open source and free features that make the initial investment is small. Provide rich functionality, not only to meet our current needs, but also to meet future expansion needs. Therefore, in our system using Mule to assemble and deploy the service. In the last article, the lack of paper and directions for future research.
|