SOA Reference Architecture - Operational Systems Layer (III)

This layer is responsible for the runtime and deployment infrastructure.

Service Delivery


  • Solution Component : provide functional capability of the services
  • Implementation Controller (IC) : Delegates request to the appropriate Solution Component. Incorporates (de-)composition of legacy systems into Solution Component.
  • Integration Layer | Integration Controller : coordination and brokering interactions between ABBs.
  • Application (Packaged and Custom) 
  • Legacy Systems
  • DB
  • Quality of Service Layer : Policy Enforcer, Access Controller

Runtime Environment

  • Runtime Hosting Environment (RHE) : support for operational and runtime services
  • Solution Platform : JVMs, CICS environment...
  • Solution Building Block : runtime component of ABBs from other layers
  • Deployment Unit : executable application (exe, war, ear...)

Virtualisation and Infrastructure Services

  • Hardware
  • Virtualised infrastructure : use of shared disk space in a cloud environment
  • Quality of Service Layer : IT Systems Manager, Security Manager

Inter-Relationships between ABBs 


  1. Requests validation by the Access Controller ABB and Security Manager ABB (Quality of Service Layer)
  2. Translation in Solution Component ABB requests by the Implementation Controller ABB
  3. Request execution by the Solution Components

Intersection with vertical Layers

  • Quality of Service Layer : authenticate / authorise for service invocation, policies enforcement, monitoring
  • Information Layer : store/retrieve metadata
  • Integration Layer : invoke business processes and/or services
  • Governance Layer : store business rules, manage policies, security policies

Intersection with horizontal Layers

Provide runtime environment for functional layers.

Virtualisation Considerations (Cloud based)

  • Isolation services : multi-tenancy, data privacy, audit, authorisation, authentication and access control
  • Application support services : dynamic resource (de-)provisioning, service location awareness, infrastructure QoS management
  • Data integrity services : recovery, high availability (cluster), backup, data QoS management, data mobility
  • Infrastructure accounting services : chargeback services, config management, capacity management

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