Day 1: Decompose by Business Capability
Decompose by Business Capability is a way of deciding where to cut a system into microservices.
Decompose by Business Capability is a way of deciding where to cut a system into microservices.
Client-Side UI Composition splits one large single-page application into several smaller front-end applications ("micro-frontends") that are built, tested, and deployed independently by different teams.
Server-Side Page Fragment Composition means the server (or an edge layer in front of it) builds one HTML page by stitching together HTML fragments that are each owned, built, and deployed by a different service or team.
A consumer-driven contract test lets the team that *calls* an API write down exactly what it needs from that API (requests it sends, response fields it reads).
A service component test starts one real microservice (its real controllers, validation, business logic, EF Core mappings and messaging code) inside a test process, replaces everything *outside* the service boundary...
The Strangler Fig pattern replaces a legacy monolith gradually instead of rewriting it in one go.