Case Study · Business Platform
22 microservices in a shared business system.
CRM, calculators, quotes, contracts, documents, knowledge base and reports in a financial advisory platform.
Architecture22 microservices
Codebase~1.4 million lines
Contribution~40%
RoleSenior full stack + DevOps
The system question
How does the platform stay coherent without every part being tightly coupled?
Shared authentication and business concepts were needed, while each service had to remain independently developable.
Business capabilities
It is not the number of services, but the responsibility boundary that matters.
CRM
Calculators
Quote generation
Contract generation
Document management
Knowledge base
Reporting
Shared authentication
Shared business models
CI/CD
Engineering lessons
Microservices are not a goal, but an organisational and responsibility decision.
- 01
Data ownership
Every piece of data has a clear owner.
- 02
Shared concepts
Must not create hidden dependencies.
- 03
Cross-service flows
Must remain traceable.
- 04
Operational cost
There is always overhead.
Pre-publication measurement
The next version requires business outcome data.
usersthroughput timestability
Next step
Is your system size already blocking change?
Platform Evolution is not automatic rewriting. We first map the responsibility and operational constraints.