About

  • Blog
  • Customers
  • Our Team
  • Why Zoom
  • Features
  • Careers
  • Integrations
  • Partners
  • Resources
  • Press

Download

  • Meetings Client
  • Zoom Rooms Client
  • Browser Extension
  • Outlook Plug-in
  • Lync Plug-in
  • iPhone/iPad App
  • Android App

Sales

  • 1 888 799 9666
  • Contact Sales
  • Plans & Pricing
  • Request a Demo
  • Webinars and Events

Support

  • Test Zoom
  • Account
  • Support Center
  • Live Training
  • Feedback
  • Contact Us
  • Accessibility
Copyright ©2026 Zoom Video Communications, Inc. All rights reserved. Privacy Policy·Terms of Service·Copyright/Trademark Takedown·Do Not Sell My Personal Information·Cookie Preferences
Gallery
CategoriesMeeting BackgroundsInsightsUser SpotlightCommunity Guidelines
Categories
Meeting BackgroundsInsightsUser SpotlightCommunity Guidelines
  1. Gallery
  2. Templates
  3. Whiteboard
  4. Microservice architecture

Microservice architecture

This template helps teams design and communicate a microservice architecture by mapping services, their responsibilities, and how they interact with each other. It provides space to illustrate service boundaries, data ownership, and integration points such as APIs or messaging systems. By visualizing the system at a service level, the template supports better architectural discussions, dependency management, and alignment across engineering and product teams.

ZW
Zoom Whiteboard235 templates
253 Views
2 Download

More like this

Categories

🫟
Design
Work iconWork

Info

Hexagonal architecture

Hexagonal architecture

Microkernel architecture

Microkernel architecture

Space based architecture

Space based architecture

Event driven architecture

Event driven architecture

Layered architecture

Layered architecture

Loading...

Overview

Design and document a microservices architecture with this comprehensive reference template. Mapping individual services, their APIs, data stores, and communication patterns, this template gives engineering teams a shared visual foundation for microservice design reviews, incident response, and onboarding.

Key Features

  • Individual service boxes with API endpoint annotations
  • Synchronous (REST/gRPC) and asynchronous (message queue/event bus) communication connectors
  • Dedicated data store blocks per service for database-per-service pattern
  • API gateway and service mesh layer
  • External client and third-party integration zones

How to Use

  1. Add a box for each microservice using the Shapes tool — label each with the service name and its primary responsibility
  2. Draw API connections using the Connector tool — use solid lines for synchronous calls and dashed lines for async/event-driven communication
  3. Add dedicated data store blocks below each service — label the database type (PostgreSQL, MongoDB, Redis, etc.) using the Text tool
  4. Include the API gateway layer at the top to show how external clients interact with internal services
  5. Annotate communication patterns with method names, topics, or event types using short text labels on each connector

Benefits

Microservices architectures are hard to hold in your head. A shared visual map makes system relationships legible — reducing the mean time to understand an incident, onboard a new engineer, or evaluate the impact of a proposed change.