C3.1 Conceptual Integration
These techniques cover the conceptual and architectural integration design between microservices.
L20 describes the service cut as the primary pain of microservices at design time. Inferring from our experience, the service cut shapes the whole architectural landscape that needs to cope with the trade-offs made by the service cut.Stakeholder Roleโ
The distinguishing stakeholder role of this category is the software architect. The main focus is planning from a macro-level perspective and incorporating cross-cutting concerns like user authentication.
Techniquesโ
๐๏ธ Service Cut
9 items
๐๏ธ Data Flows
3 items
๐๏ธ Workflows
2 items
๐๏ธ Storage Management
2 items
๐๏ธ Location of Business Logic
2 items
๐๏ธ User Auth
4 items
๐๏ธ UI Integration
4 items
๐๏ธ Conceptual Error Handling
4 items