SysFEAT - Systemic Framework for Enterprise Architecture & Transformationk

BUILDING BLOCK - MicroService

Description	A MicroService is a small autonomous unit of software, emphasizing self-management and lightweightness as the means to improve software agility, scalability, and autonomy. 1) MicroServices are automous or assembled and orchestrated as components of Applications. 2) MicroServices can be directly deployed to Computing Systems. MicroServices are both a logical unit of software and a Deployable Package. 3) MicroServices owns their own data store and dot not have any shared stores with other components. MicroService is a Micro enterprise asset that sits at the lower level of Business Software System decomposition.
External references	C4 Model - Level 2 - Container Diagram, C4 Model - Level 3 - Component Diagram, Martin Fowler - Micro-Service, Microsoft - Architecture Design - Microservice architecture style, OpenGroup - ArchiMate - Application Component
Super Types	Software Module (from partition: Systemic Levels of Software Module) Deployable Package Micro Business System Software Module
Functional Domain	Application Functional Architecture The Application Functional Architecture domain is used to describe the functional structure and behavior of Business Software Systems. Application Deployment Architecture The Application Deployment Architecture domain defines concepts used to organize Applications in Deployable Packages.
Dictionary	Dictionary of SysFEAT concepts
Systemic Levels	Micro
Lexical Scope	Architecture Container
Framework Mapping	ArchiMate - Application Layer : Application Component - Micro

RELATIONSHIPS

Simple Graph Graph & Inheritance Table

Simple Graph

Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝

Relationship Table

Relationship	Cardinality	Target Entity	Source Entity	Description
Specialized Package	[*..0]	Deployable Package	Deployable Package
Packaged Application	[1..1]	Application	Deployable Package
Required Software Technology	[*..0]	Software Technology	Deployable Package
Specialized Software System	[*..0]	Business Software System	Business Software System
Realized Logical System	[*..0]	Logical Software System	Business Software System
API Service Point	[1..1]	Application Interface	Business Software System
API Request Point	[1..1]	Application Interface	Business Software System
Software Connection	[*..0]	Application Interface	Business Software System	An Interaction represents a contract between entities in a specific context inside or outside a company. These entities can be organizational units, activities, or processes.The content of this contract is described in a protocol.
Physical data store	[*..0]	Physical Data Domain	Business Software System
Realized Software System	[1..1]	Business Software System	Concrete Software System
Physical Service Point	[1..1]	Physical Software Interface	Concrete Software System	A Physical Service Point is a connection point allowing opening a communication to a technical architecture or an application technical area that complies with a specified communication protocol (SMTP, HTTP, etc.).
Physical Client Point	[1..1]	Physical Software Interface	Concrete Software System	A technical output port is a point that allows asking to open a communication line from a technical architecture or an application technical area and that complies with a specified communication protocol (SMTP, HTTP, etc.).

TEXTUAL SYNTAX

SEMANTIC TAXONOMY

Sub-Types Super-Types

Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.

BORDERS

Name	Super type	Border Type	Description
API Request Point	Business Agent::Business Request Point	Application Interface
API Service Point	Business Agent::Business Service Point	Application Interface
Physical Client Point	Technology System::Technology Request Point	Physical Software Interface	A technical output port is a point that allows asking to open a communication line from a technical architecture or an application technical area and that complies with a specified communication protocol (SMTP, HTTP, etc.).
Physical Service Point	Technology System::Technology Service Point	Physical Software Interface	A Physical Service Point is a connection point allowing opening a communication to a technical architecture or an application technical area that complies with a specified communication protocol (SMTP, HTTP, etc.).