Microservices diagram

Draw microservices with the logos of what they run on: a Go orders service, a Spring Boot payments service, PostgreSQL, Redis and Kafka, inside a Kubernetes cluster. It opens with that example, ready to change into your own system.

Services with their technology

A service shape shows its language or framework (Go, Java, Spring Boot, Kotlin, .NET, Node.js, TypeScript, Python, Rust, PHP, Ruby), and databases, caches and queues show theirs (PostgreSQL, MySQL, MongoDB, Redis, Kafka, RabbitMQ, NATS, SQS and more). Change a shape's technology in the format panel and its logo, colour and label follow, while its place and connections stay.

Calls and events

Set each connector's type: a call (solid line, filled arrow) for a request that waits for an answer, such as REST or gRPC, or an asynchronous message (dashed line, open arrow) for an event published to a topic or queue. Telling the two apart shows which services need each other to be up.

Boundaries and platform

Kubernetes clusters and namespaces, Docker hosts, VPCs and bounded contexts are containers: put services inside to show where they run or which domain they belong to. Gateways and platform tools (Kong, NGINX, Envoy, Istio, Keycloak, Vault, Consul) and observability tools (Prometheus, Grafana, Jaeger, OpenTelemetry) have shapes too.

Questions

How do I show a database per service?

Draw a database next to each service and connect only that service to it. When no other service has an arrow into it, the ownership is plain to see.

Where do the logos come from?

From Simple Icons; they remain trademarks of their owners. Brands that are not in Simple Icons, such as Java and AWS products, get a lettered badge instead.

Can I export it for a design document?

Yes: as PNG or SVG, or copied as an image. The logos are part of the drawing, so the export looks the same as the canvas.