img
Home > Design Patterns > Micro Task Abstraction

Micro Task Abstraction (Erl, Naserpour)

How can single-purpose logic with specialized processing requirements be separated and governed independently?

Micro Task Abstraction

Problem

Grouping single-purpose logic with specialized processing and deployment requirements together with other types of logic that does not have such requirements can compromise the former's ability to consistently fulfill its requirements.

Solution

An individual unit of single-purpose logic with specialized processing and deployment requirements is separated into a functional context with a narrow functional scope to become the basis of a microservice.

Application

The pattern is applied during a pre-design analysis stage. Subsequently, each microservice architecture can be individually tailored in support of fulfilling the specialized processing and deployment requirements.

The logic is separated into granular, single-purpose functions (or “micro-tasks”) that form the basis of individual microservice implementations.

Micro Task Abstraction: By applying the Micro Task Abstraction pattern we identify single-purpose tasks that form the basis of microservice deployments.

By applying the Micro Task Abstraction pattern we identify single-purpose tasks that form the basis of microservice deployments.

This pattern is typically applied during the pre-design analysis stages, as explained in the complete pattern description.

Module 10: Advanced Microservice Architecture & Containerization.

This pattern is covered in Module 10: Advanced Microservice Architecture & Containerization..

For more information regarding microservice and containerization courses and accreditation,
visit the Microservice Architect Certification program page..