Service-Oriented Architecture

Service-Oriented Architecture

Service-Oriented Architecture is a group of services that communicate with each other. The communication process involves either simple data passing or two or more services coordinating activities. Intercommunication implies the need for some means of connecting services to each other. This allows companies to unify its process by structuring large applications into a collection of smaller services. Companies have the ability to access the information from both inside and outside the organization. New applications may also be derived from the global pool, which can lead to greater flexibility and uniformity. Unfortunately, some companies may have difficulties pulling the data together. This can be attributed a great deal of data being stored in different areas. As more businesses use service-oriented architecture, they will find that middleware can be an invaluable resource. Middleware serves as an adhesive. It is the glue which connects software components and applications. Processes have the ability to run on one or more machine to interact across the network. This technology evolved to provide for interoperability in support of the move to coherent distributed architectures, which are used most often to support and simplify complex, distributed applications. Web servers, transaction monitors, and messaging and queuing software are a few examples. The following guideline principles define the ground rules for development, maintenance, and usage of the service-oriented architecture:

• Reuse, granularity, modularity, composability, componentization, portability, and interoperability

• Standards compliance

• Service identification and categorization, provisioning and delivery, and monitoring and tracking

An enterprise service bus is software infrastructure that simplifies the integration and flexible reuse of business components within a service-oriented architecture. An enterprise service bus does provide a reliable...