SOA Patterns > Logical Inventory Layer Patterns > Micro Task Abstraction
Micro Task Abstraction (Erl)
How can non-agnostic logic with specialized processing requirements be separated and governed independently?
Problem
Grouping non-agnostic logic with specialized processing and deployment requirements together with non-agnostic logic that does not have such requirements can compromise the former’s ability to consistently fulfill its requirements.
Solution
Individual units of non-agnostic logic with specialized processing and deployment requirements are separated using the microservice model and abstracted into a microservice layer in which there is the architectural freedom to tailor environments in support of specialized service processing and deployment requirements.
Application
Once non-agnostic business process logic has been separated from agnostic logic, it is reviewed to identify units of logic with specialized processing and deployment requirements suitable for the microservice layer.
Impacts
The abstraction of micro task logic into a separate service layer can introduce analysis, design and governance overhead. The Microservice Deployment [xxx] pattern is commonly applied to micro task logic in order to realize the necessary service deployment environment. This can introduce disparate communication protocols and further demand specialized implementation technology that may impose new infrastructure, administration and governance requirements.
Architecture
Inventory, Composition, Service
Select non-agnostic logic with specific performance and/or reliability requirements is separated into microservice candidates.
This pattern is covered in SOACP Module 4: Fundamental SOA Analysis & Modeling with Services & Microservices.
For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.