SOA Reference Architecture : Introduction (I)

In this new series of articles, I'll present briefly the Service Oriented Architecture (SOA) concept.

You can find useful information on the SOA Reference Architecture.

The benefits of using an SOA approach are mainly:

  • Reducing cost
  • Agility
  • Increase competitive advantage
  • Faster time to market
  • Consolidation of systems
  • Better align IT to business goals
The SOA Reference Architecture (SOA RA) provides an abstraction for SOA-based solutions.

The SOA RA gives us an abstraction using common layers:

Cross-cutting (vertical) Layers:

  1. Integration Layer : mediation / routing / protocol transformation
  2. Quality of Service Layer : manage Non Functional Requirements (NFRs)
  3. Information Layer : data needed for horizontal layer creation
  4. Governance Layer : Manage policies and business rules (registries / repositories)

Functional (horizontal) Layers

  1. Operational Systems Layer : runtime environments for all layers
  2. Service Component Layer : services implementation
  3. Service Layer : services contract
  4. Business Process Layer : call services for providing business capabilities
  5. Consumer Layer : GUI call services via integration layer (or directly via service layer)

Logical Solution View of the SOA RA

Because the provider and the consumer may be different organisations, the service Layer must be the decoupling layer between them. SOA is then the foundation of Cloud Computing and SaaS.

Comments

Post a Comment

Popular posts from this blog

Spring JPA : Using Specification with Projection

You may probably know that using Specification with Projection is not possible at this moment. I'll show you how you can easily bypass this problem using the JPA Criteria. 1. Create an extended repository We begin by creating an extending global repository as follow : You can find more information here . 2. Add our custom method In order to limit the fields returned for each item, the consumer of my API must provide the required fields this way: /orders?fields=productId,name,quantity . ( Best Practices ) Basically, I'm defining the SELECT clause with the returned fields (cf. getSelections() ): 😎Happy coding...
Read more

Chip input using Reactive Form

The Chips component documentation from the angular material website, describes how to use the MatChipInput directive with a chip-list for adding or removing chips. I'll show you how you can implement the same component using Reactive Form. The HTML template: The TS component file:   As you can see, we use the FormBuilder class to simplify the form creation. We define our requirements as a  FormArray within our FormGroup. The requirements will be accessed in our template with this expression inside the *ngFor of <mat-chip></mat-chip> : *ngFor="let requirement of form.get('requirements').controls; let i = index;" In the ChipComponent class, the requirements array is accessed by using this expression: this.form.get('requirements') as FormArray; Thanks
Read more