Skip to content
Microservices architecture diagram with an API gateway, auth service, three services with their databases and a message broker on a card over a photo.

Microservices Architecture Diagram

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

Clients call an API gateway over HTTPS. The gateway checks the bearer token with the auth service, then routes each path to the orders, catalog or payments service, using service discovery to find a healthy instance. Each service reads and writes only its own database. When an order is placed, the orders service publishes an OrderPlaced event to the message broker, and the notification service consumes it to send email and push messages. Every service sends logs, metrics and traces to shared observability.

The design point is that services share data only through APIs and events, never through another service's database. Each team can change its schema and release cycle freely, but data is eventually consistent across services. Event handlers must be idempotent because the broker delivers each message at least once. Start with one team per service and split further only when a boundary has proven stable. To adapt it, rename the services and choose the gateway and broker that suit your stack.

Useful for

  • Splitting a monolithic shop into orders, catalog and payments services
  • Setting service boundaries and database ownership for a new platform
  • Adding an event broker so notifications stop being called directly

What's included

  • A designed cover slide
  • The diagram: 13 components and 12 connections as editable shapes
  • A components table and the 7-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename Web and mobile clients, API gateway, Auth service and the other boxes inside Service network (private) to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 7-step data flow and the 8-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download microservices-architecture-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

Why does each microservice get its own database?

A separate database lets a service change its schema without coordinating with other teams. Services share data through APIs or events, so no other service depends on its internal tables.

What does an API gateway do in a microservices system?

The gateway is the single entry point. It terminates TLS, checks tokens, applies rate limits and routes each path to a service, so clients do not need the address of each service.

Why must consumers of a message broker be idempotent?

Most brokers deliver each message at least once, so a consumer can see the same event twice after a retry. An idempotent handler gives the same result on a repeat, so a duplicate OrderPlaced event does not send a second email.

  • #software-design-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…