Skip to main content

C4 - Integration Within a Microservice

These techniques apply for the integration within a microservice and its responsible team.

Each microservice is a silo from top to bottom, potentially internally integrating with database(s), user interface(s), and further components L49. Scaling is facilitated horizontally by deploying multiple instances, introducing the challenge to coordinate these instances L20.

Level of control over integration counterpart​

The control over the integration counterpart is high since the microservice's team is fully responsible for all its components. Integration within a microservice benefits from the considerably lower communication effort within a single team than coordinating with other microservices teams LN43L32L8.

Communication channels within a team can be more informal and adhoc, and are well exercised: "[...] I can't imagine how we'd organize ourselves without a chat system. The cross-functionality and the inherently fast, efficient, and constructive communication is key. Email distribution would have slowed us down during implementation - it's an outdated method of communication" - [Interview A, translated from German]

Refined Categories​