Is this a good way to represent systems architecture or am i missing anything?

Tech with Thiru — Fri, 24 Oct 2025 23:40:15 GMT

I gave it a shot at this systems architecture diagram. I am curious to learn whether this is the right way to put one together or am i missing something?

A basic systems architecture depicting the following:

Business Capabilities.
Users, Authentication & Authorization using Azure AD
Front-end Web & Mobile Applications
Backend services and the protocols used for communication - REST/SOAP/gRPC/Async Message based communication.
Integration Layers (most important) - APIM, Azure Functions, Logic Apps, App Services, On-premise services, External Systems,
Message brokers - Azure Service Bus, RabbitMQ, Kafka
Data Layer - Azure SQL, Azure Data Factory, SSIS.

What I’m looking for feedback on:

Service boundaries and modularization
Any missing best practices for Azure architecture
Overall clarity and readability of the diagram

Am I missing something that is not illustrated in the diagram?

Here is the diagram for your reference:

The top section has a verbose representation of the architecture, and the bottom has the same architecture represented with Azure icons.

drawio: https://www.dropbox.com/scl/fi/h38oor38rauiwzg0789ek/sys-arch.drawio?rlkey=cd1ki3fzhk38pcrk84wpua587&st=h3cm8ama&dl=0

png: https://www.dropbox.com/scl/fi/yc1bo923f165uk14oozps/sys-arch.png?rlkey=k0lwhs0oj553co4h9p2n8zy4z&st=dg3xyhn9&dl=0