Everything is a service: Now it is time SOA has arrived, but can it go far?
Author: Daryl Plummer
"People are service and driven", "I always remember this sentence in the days of the system design. Every morning (or night, depending on your habits), we carry out the shower and use water "service" to clean our own. If the phone is ringing, or your neighbor's cat is forced by your Rottwell to the way, you will stop the shower and turn this "event." If you respond to the phone bell event, you will use a phone "service", and if you rescue the furry little guys from the Rotel Well's claw, I think your neighbor (people who like to raise cats) ) Will think this is a service. Therefore, people are serving and driven by events. The system should also be serving and driven by events. Gradually, we have to deliver flexible systems that can respond to individuals, partners, or the entire value chain. "Market of One" proposed by Michael Dells is pushing a system that can respond in real time. The majority of partner networks are intended to integrate system with amazing speed. The expanded supply chain system enables us in a multi-company business process network, and the network is mostly in the flexibility. Service-oriented service helps us implement the above.
Service-oriented frames in Gartner, we quite discuss the service-oriented architecture (SOA). Today, an event-driven architecture has also begun to increase the slope of the Hype Cycle of the Technical Maturity. These two concepts are combined to enable us to build a framework to describe some key areas, while in which services are changing the design, deployment, and use system (see Figure 1). Service-oriented architecture (SOA): The basic topology of the service-oriented system includes customers, interfaces, and providers. Customers use interfaces to request "service" from the provider. When deploying services, you must ensure that the service does not affect our customers because customers can only see the interface. No longer need to define architecture for each application, SOA has become the default standard. Service-oriented Application Development (SODA): If you are building an application based on SOA, you will find that the use of services is developing and the development of traditional sense is not exactly the same. If you haven't seen this, you just have to wait, but your Rottwell dog has begun to act. The use of services seems to be very simple, but there are many potential problems, such as composite services that need to simulate service behavior, assembly cannot be interrupted, modeling business processes to get the right behavior, and handling services to you but do not have. modify. SODA is a concept that describes how to handle these issues (see Figure 2). The SOA system can be very flexible, but if there is no correct development plan, there is no SODA, they will become quite unflexible. Service-oriented Business Applications (SOBA): This is the last item in the service policy, or it may be the most critical. The packaged business app is a new service to build a workshop. We will see that unfunctuous individual packages are redesigned as a set of services that interact with each other. The essence of application definitions is changing. More critical is that the barriers between the infrastructure, development and applications are disappearing. Within 5 years, we will see the integration of these layers to eliminate them and support the difference between the products that use their products. Event-driven architecture (EDA): From simple to complex event processes, the ability to send and handle events is more important. SOA and events are complementary because events can call services. Complex event processing will become the next obstacle to overcome.
Why is it now? You may say: "I have already listened enough. Why will it work this time?" Well, let me answer this question simply. First, the Web service has spawned new influence in the service. We rarely see that the basic standards are accepted by each industry. Second, the need for the flexible IT system is no longer a choice, but it has become a top priority, which is the need for business. Also, the use of Internet has weakened our prejudice to the use of "other people". Finally, the application platform kit is a multi-group integrated technology, which makes everything that the service is more easily and feasible. Can it fail? of course. In the IT industry, we don't know what it is for stranded technical strategies. You can wait, you can observe or act for your own benefits. So, stop the shower and save the kitten. Everything that has been served has arrived. What you have to do is planning it, not let it happen to yourself. Value will be reflected. People are service-oriented and driven by events. If you don't believe me, you should also believe this. About the author DARYL PLUMMER is the group vice president and chief researcher of Gartner Inc. He is a major analyst in Web services, application development and architecture.
