SOA architectural style

SOA architectural style

1. The modeling and design methodology for SOA applications it is known as service-oriented analysis and design. The service-oriented architecture is both a framework for the software development as a framework for implementation work.

   • LAYER 1: Operational Systems. This layer consists of existing applications within the company, known as legacy systems. Among these layers we can have CRM's, ERP's, BI applications, Object Oriented, etc. All these applications are integrated through SOA.
   • LAYER 2: Component Layer: This layer is the one that contains the components that are responsible for providing the functionality exposed by the services.
   • LAYER 3: Services Layer: In this layer reside the services that the organization decides to exhibit. They can be discovered, referenced directly, or be part of an orchestration or of a composite service.
   • Layer 4: Business Processes - Orchestration: In this layer the orchestrations of the services are exposed. The services are linked to these workflows, and therefore act as a single application.
   • LAYER 5: Presentation Layer. Normally this layer is not part of SOA, but every day it becomes more relevant. Users access services and orchestrations by invoking the functionality they want to consume from various user interfaces.
   • LAYER 6: Integration (ESB - Enterprise Service Bus). This layer facilitates the integration of services through the introduction of a set of capabilities such as routing, protocol mediation, transformation mechanisms, etc.
   • LAYER 7: Administration, Monitoring and Service Quality. This layer gives us the characteristics required to monitor, manage and maintain the quality of service in areas such as security, performance, and availability. It is known as SOA governance.