Integration for Software Design and Architectures
Integration covers how parts of a system communicate and share data. It includes API styles such as REST, gRPC and messaging, versioning and contracts, and data architecture choices like database per service, replication and eventual consistency, all of which decide how loosely services stay coupled.
Stage: Architectural Styles · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026
What to learn in Integration
- Compare REST, gRPC and message queues for a use case
- Version an API without breaking existing clients
- Publish and consume events with a message broker
- Explain database per service and the cost of cross-service joins
- Use an outbox pattern to publish events reliably
- Choose between shared database and API integration
Integration interview questions
Why is a shared database between services discouraged?
It couples services through schema, so one team's change can break another, and it hides dependencies. Each service owning its data and exposing it through APIs or events preserves independent change and clear ownership.
What problem does the outbox pattern solve?
It avoids the dual-write problem, where updating a database and publishing a message can half-fail. The service writes the event to an outbox table in the same transaction, and a separate process reliably publishes it.
Where Integration fits in the Software Design and Architecture roadmap
Integration belongs to the Architectural Styles stage (advanced level), which takes about 30 hours. Structure systems.
Other units in this stage
Back to the full Software Design and Architecture roadmap