Yila

Figure template · System & Network · 4:3

Microservice System Topology with API Gateway and Async Messaging

Synchronous request paths sit on the left behind an API gateway, event-driven consumers sit on the right around a message broker, and solid blue versus dashed orange lines keep the two styles apart. Suited to systems papers and software engineering teaching.

Updated Oct 16, 2026Reviewed by Roxy Liu10.75K1.89K

Prompt

Create a scientific figure about: Microservice system topology with gateway and async messaging. Visual style: Clean Vector. Requirements: - publication-ready scientific quality - clear labels and directional arrows where appropriate - avoid cartoon style, avoid meme style, avoid stock-photo look - avoid neon glow and over-sharpened CGI look unless explicitly requested - composition optimized for research papers and academic slides - category context: systems-networks - flat vector look with crisp boundaries and minimal gradients - white or very light background for publication clarity - high legibility labels with consistent typography

What this template is

The diagram models a small e-commerce backend. External clients talk only to an API gateway, which handles entry, security and authentication, routing and rate limiting before making blocking HTTP or gRPC calls to user, product and order services, each with its own database. The order service publishes events to topics and queues on a message broker; inventory, notification and analytics services consume them asynchronously, updating stock, sending confirmations through an external notification API and feeding a data warehouse. A reader should leave knowing which calls hold up a request, which work is decoupled into the background, and why every service owns its data.

Elements to label

  • External clients

    A phone and a laptop icon at far left; name the client types and keep all request arrows pointing at the gateway.

  • API gateway

    A tall blue block split into entry point, security and auth, routing and rate limiting; adjust the list to your system's responsibilities.

  • Synchronous services and databases

    Green user, product and order service boxes, each sitting on its own database cylinder; label the protocol on the connecting arrows.

  • Async event publication

    A dashed orange line from the order service into the broker, annotated as event publication to set it apart from requests.

  • Message broker topics and queues

    A large orange block listing named topics and queues; each name should match exactly one publisher and its subscribers.

  • Event consumers

    Orange inventory, notification and analytics boxes, captioned with what each does: updates stock, sends confirmations, produces metrics and reports.

  • External system and data warehouse

    A dashed grey box for the external notification API and a cylinder at bottom right for the analytics data warehouse.

  • Legend

    Separates blocking synchronous from non-blocking asynchronous communication and gives shapes for microservice, database and external system.

Where it is used

  • Paper mechanism figure
  • Defense slides
  • Course handout
  • Academic poster

What reviewers look for

  • Delivery semantics

    Reviewers will ask whether the async path promises at-least-once or exactly-once delivery, whether consumers are idempotent, and where poisoned messages go, for example a dead-letter queue.

  • Consistency across service databases

    Is the order write and its event published atomically, and how is a failed stock update compensated? If you rely on an outbox or saga, mark where it sits in the topology.

  • Topic and queue naming

    The sample lists the same payment-completed queue twice, and no payment service in the diagram ever publishes it. Every topic should have a clear producer and at least one consumer.

  • Return paths and failure handling

    Only the product service shows a response arrow; user and order calls look one-way. State timeouts, retries or circuit breaking for synchronous calls so readers do not mistake them for fire-and-forget.

How to use it in Yila

  1. 1Pick a figure
  2. 2Describe your subject and the steps to stress
  3. 3Refine it in chat, then download the PNG

Tips

Do

  • Rename the services to your real components, such as an inference or feature service, so the diagram matches your paper.
  • Keep only the topics your experiment actually uses inside the broker block, each with its publisher named.
  • If you report latency, ask Yila to add a measurement-point label on both the synchronous and asynchronous paths.

Avoid

  • Leaving a duplicated queue name in place; a reviewer will read it as a sign the topology was not checked.
  • Mixing solid and dashed lines between the gateway and services, which defeats the legend.
  • Keeping the misrendered SMS example in the notification box; ask for it to be redrawn or remove the example.

Questions

Can this architecture diagram go straight into a systems paper?

Use it as a first draft. It is an AI-generated illustration, and its services and topics are generic examples. Swap in the components you actually deployed, remove the duplicated queue name and confirm the direction and communication style of every arrow before submission.

Can I add or remove services, or redraw a connection?

The image is not editable element by element and is not a vector graphic. Keep chatting in Yila instead, for example ask for a payment service that publishes payment events, or for the gateway to show a caching layer, and the whole topology is regenerated from your description.

What format is the output?

An AI-generated PNG image in a 4:3 landscape frame, which fits a slide or a single-column paper figure. If a conference template demands vector graphics, use the PNG's zoning as a blueprint and redraw it in your diagramming tool.

Is it free?

Viewing this page and the sample is free of charge. Generating a diagram in Yila, and each revision after it, consumes credits. New accounts receive 2,500 credits, enough to produce a first version and then tailor service names, topics and arrows to your own system.

Can it show a service mesh or a multi-zone deployment?

Describe sidecar proxies, a control plane or availability-zone boundaries in your prompt and Yila rearranges the layout. Crowding grows quickly, so consider one figure for the logical topology and a separate one for the deployment view.

Can I contrast this design with a monolith or a synchronous-only version?

Ask for a side-by-side comparison panel. Yila can draw a second, simpler topology next to this one so readers see what the gateway and broker change, which helps in the motivation section of an architecture paper.

Download sample PNG