Compute Engine web application
Show a load balancer, Compute Engine instances, and Cloud SQL, with Cloud Storage for application assets. Mark VPC, subnet, and zone boundaries, and show which application components depend on the database.
Arcentry for Google Cloud
Explain how your Google Cloud services work together, from Compute Engine workloads to GKE clusters and serverless applications. Build an interactive GCP architecture diagram in 2D or 3D, and bring the networks, data flows, and external dependencies into the same picture.
A Google Cloud architecture diagram connects service names to the way an application actually works. Compute Engine instances, a GKE cluster, or Cloud Run services only become useful documentation when readers can see the traffic, data, and dependencies around them.
Arcentry provides an editable canvas for that context. Arrange Google Cloud components, draw connections, and add labeled areas for the boundaries you need to explain. Present a 2D overview or an isometric 3D view for design discussions, migration planning, and onboarding.
Use project, region, and zone labels when they help a reader understand placement or ownership. Keep network boundaries distinct from application groupings: a logical service group and a VPC communicate different things, even when they overlap in the design.
For data architectures, show the producer, processing stages, storage, and consumers. Label whether a connection represents a request, an event, or a batch transfer. This makes it easier to review a pipeline without asking every reader to infer its behavior from product icons alone.
Share an exported diagram in a design document, or publish an interactive embed that readers can explore. Include the open-source tools and third-party APIs alongside your Google Cloud services so the view reflects the full application.
Use Arcentry’s REST API to maintain selected objects, labels, and metadata from your own workflow. Start with the free plan and expand the diagram as the questions your team needs to answer become more detailed.
Architecture ideas
Plan a virtual machine deployment, explain a container platform, or trace data through a pipeline. Each view emphasizes a different set of relationships in your Google Cloud architecture.
Show a load balancer, Compute Engine instances, and Cloud SQL, with Cloud Storage for application assets. Mark VPC, subnet, and zone boundaries, and show which application components depend on the database.
Map container workloads on Google Kubernetes Engine or Cloud Run alongside ingress, APIs, and backing services. Make service-to-service calls explicit and show where the application reaches outside its cluster or serverless environment.
Trace events through Pub/Sub and processing in Dataflow toward BigQuery and downstream consumers. Label the stages and data movement so engineering and analytics teams can discuss transformations, responsibilities, and dependencies.
From design to documentation
Start with Compute Engine, a container workload, or a data pipeline. Add the Google Cloud services and external systems needed to explain that view, instead of filling the canvas with unrelated resources.
Group resources by project, region, zone, or network where useful. Draw labeled connections for requests and data movement, and distinguish logical application groups from the boundaries of your cloud deployment.
Export images for technical documents or share an interactive embed. Add metadata and use the REST API to update selected parts of the diagram as your application and its documentation evolve.
Good to know
Have a question about your workflow? Write to info@arcentry.com.
Pair your diagram with the provider's technical guidance.
Yes. Use Compute Engine components alongside load balancing, databases, and storage. Group virtual machines by application or deployment boundary, and add labels to explain zones, instance groups, and network relationships.
Both names refer to the same platform here. Arcentry supports Google Cloud architecture diagrams, including services commonly searched for as GCP. Compute Engine is one part of Google Cloud, alongside container, serverless, networking, and data services.
Yes. Connect services such as Pub/Sub, Dataflow, BigQuery, and Cloud Storage, then add the applications or external systems that produce and consume data. Use directional lines and stage labels to make the flow clear.
Yes. Mix providers, open-source software, and on-premise components on one canvas. This is useful for migration diagrams, shared data flows, and applications whose dependencies span several environments.
Yes. Create diagrams manually in Arcentry without connecting your cloud account. The free plan requires no credit card. If you want live updates, send selected information from your own systems through Arcentry's REST API.
Make the system visible
Make the compute, services, and data flows behind your application easier to understand.