technicaldiagrams.com
← Architecture

Service architecture

Show the boundaries and connections in a small system.

Service architectureExplain a request moving from a client through services to storage. All values are illustrative example data.A request, end to endHTTPS → application → persistenceApplication boundaryWeb clientbrowserAPI gateway/v1/eventsPostgresprimary storeQueueasync jobsrequestwritepublish
Live SVG · all content is illustrative

Make it yours

Edit labels & content

Change the text directly. Use the scene editor to move or add elements.

Edit individual elements

Choose a shape or text element, then change its properties. Related labels and connectors have separate coordinates.

Edit scene JSON

Change positions, dimensions, paths, and labels. Apply validates the scene before changing the preview. Primitive reference ↗

Review this diagram

These ratings help you compare how an example looks and how much work it takes to change. They are initial assessments of the example, not guarantees of correctness.

Appearance 92/100Ease of changes 94/100Overall 93/100Initial assessment

Your scores and review history stay in this browser. Export reviews to keep a copy. Read the rubric.

    Use this when

    Explain a request moving from a client through services to storage.

    Choose another form when

    You need to show timing, retries, or more than twelve services.

    Built from

    BoundaryNodeConnectorLabel

    Few aligned nodes; labels and boundaries can change without rerouting most edges.

    This example uses explicit positions. Check labels and connections after changing its content.

    Give your agent this reference

    Use the example to show your agent the form you want. Describe your system or provide your source material, then ask it to generate an adapted diagram and inspect the result.

    Includes the reference URL, current scene, and settings. Paste it into your own agent.

    Read the agent workflow ↗

    Take the source

    The SVG is self-contained. The JSON preserves editable primitives and your presentation settings. Labels remain text; shapes remain vectors.

    Original scene JSON ↗
    Controls, limits, and embedding ↗