Microservices | C4 model
c4model.com · 842 words · saved by 1 readers
The C4 model for visualising software architecture (official website)
Broadly speaking, there are two options for diagramming microservices when using the C4 model, although it depends what you mean by “microservice”. With that in mind, let’s start from the beginning. Stage 1 - monolithic architectural style Imagine that we work for a small startup company and our task is to build a software system (named “X”) that offers business capabilities A, B, and C to our customers. Our system context diagram might look like this: Arguably the quickest and cheapest way to get something delivered, especially as a young startup with a small engineering team, is to use…
saved by
related reading
- Abstractionsc4model.com
- Containerc4model.com
- Componentc4model.com
- Clean Coder Blogblog.cleancoder.com
- Microservicesmartinfowler.com
- Microservices: Decomposing Applications for Deployability and Scalability - InfoQinfoq.com
- Microservice Architecture patternmicroservices.io
- From Monolith to Microservices to Reasonably-sized Servicesperandrestromhaug.com
- Microservices vs Monoliths: What is the Future of Software Architecture? | HackerNoonhackernoon.com
- Home | C4 modelc4model.com
- Microservice Trade-Offsmartinfowler.com
- You probably don’t need microservicesthrownewexception.com