LAB navigation

Each tab keeps one lane legible: control plane, workload, modern workloads, cloud terminals, or the microservice fabric.

public site on vercel, private execution through LAB lanes
read-only until sign in
Tab 3 | Modern Workloads

Low-cost multi-tier app with cloud fanout

VCF hosts the frontend, API, and PostgreSQL tiers. AWS, Azure, and GCP provide the lightweight integration lanes: SNS/SQS, Queue, and Pub/Sub. The page walks the app through deploy, fanout, readback, and teardown without pretending the cloud cards are just status cards.

VCF app shell + AWS/Azure/GCP integrations

VCF app shell

frontend + api + postgres
Supervisor
m02-w01-cl01-sup01
Namespace
modern-workloads
Frontend
modern-web
API
modern-api
Database
modern-postgres
Worker
modern-worker
Manifest
manifests/vks/modern-workloads.yaml

Cloud integration cards

aws + azure + gcp
VCF shell
frontend + API + PostgreSQL
AWS lane
SNS topic + SQS queue
Azure lane
Storage Queue branch
GCP lane
Pub/Sub topic + subscriber
Trigger
modern workflow exercise
Teardown
modern workflow teardown
Containerized apps are deployed via the vCenter / vKS tab, while this page stays focused on the VCF-hosted app shell, the cloud integration cards, and the readback surface that keeps the fanout auditable.
>

Modern multi-tier app flow

Expand to see the phase-by-phase operator sequence for this tab.

8 phases
>
phase 01On-prem - Preflight and guardrailslive

Confirm the VCF app shell, private preview, and existing feed state before the multi-cloud app flow starts.

1 cmds
  1. 01
    Confirm the VCF app shell, private preview, and existing feed state before the multi-cloud app flow starts.
    show raw commands
    selected command
    modern workflow preflight
    raw step 01
    modern db recent
    raw step 02
    modern db count
>
phase 02On-prem - Deploy the app tierlive

Apply the modern-workloads manifest so the frontend, API, and PostgreSQL stack are in place before cloud integrations are exercised.

1 cmds
  1. 01
    Apply the modern-workloads manifest so the frontend, API, and PostgreSQL stack are in place before cloud integrations are exercised.
    show raw commands
    selected command
    kubectl apply -f manifests/vks/modern-workloads.yaml -n modern-workloads
    raw step 01
    kubectl get pods -n modern-workloads
>
phase 03AWS - AWS integration lanelive

Show the AWS branch as the managed event ingress lane with SNS fanout into SQS for the app event stream.

1 cmds
  1. 01
    Show the AWS branch as the managed event ingress lane with SNS fanout into SQS for the app event stream.
    show raw commands
    selected command
    modern workflow aws
    raw step 01
    SNS topic
    raw step 02
    SQS queue
>
phase 04Azure - Azure queue lanelive

Show Azure as the lightweight queue-backed branch that records app events and exposes the handoff for verification.

1 cmds
  1. 01
    Show Azure as the lightweight queue-backed branch that records app events and exposes the handoff for verification.
    show raw commands
    selected command
    modern workflow azure
    raw step 01
    Storage account
    raw step 02
    Storage queue
>
phase 05GCP - GCP pub/sub lanelive

Show GCP as the Pub/Sub lane that fans the app event into a subscriber for enrichment and readback.

1 cmds
  1. 01
    Show GCP as the Pub/Sub lane that fans the app event into a subscriber for enrichment and readback.
    show raw commands
    selected command
    modern workflow gcp
    raw step 01
    Pub/Sub topic
    raw step 02
    Pub/Sub subscription
>
phase 06On-prem - Exercise the fanoutlive

Insert one app event and fan it across the cloud integration lanes while the VCF feed keeps the readback auditable.

1 cmds
  1. 01
    Insert one app event and fan it across the cloud integration lanes while the VCF feed keeps the readback auditable.
    show raw commands
    selected command
    modern db insert
    raw step 01
    modern db recent
    raw step 02
    modern db latest
>
phase 07On-prem - Verify readbacklive

Confirm the modern-postgres feed and preview surface reflect the cloud fanout so the lane stays auditable.

1 cmds
  1. 01
    Confirm the modern-postgres feed and preview surface reflect the cloud fanout so the lane stays auditable.
    show raw commands
    selected command
    modern db recent
    raw step 01
    modern db latest
    raw step 02
    modern db count
>
phase 08On-prem - Teardownlive

Delete the disposable cloud signal resources, write the teardown row, and leave the VCF app shell ready for another fanout cycle.

1 cmds
  1. 01
    Delete the disposable cloud signal resources, write the teardown row, and leave the VCF app shell ready for another fanout cycle.
    show raw commands
    selected command
    modern workflow teardown
    raw step 01
    modern db recent
    raw step 02
    modern db count
live terminalmodern@lab

Modern workloads operator terminal

Use the deploy, fanout, and teardown phases to show how the VCF frontend, API, and PostgreSQL lane fans through AWS, Azure, and GCP before readback.

command lineidle
modern@lab$
Public visitors can still fill and copy commands. Sign in or create an account to browse with a member session.
operator indexfill command line

Multi

VCF

VKS

history buffer

Run a command to capture the last five entries here. Each row stays compact until you expand it.

app readback

0 rowsapi modern-apigenerated -
/api/onprem/modern-preview
database lanedb@modern

This readback lane is separate from the VM workload tab. Seed one row, exercise the fanout, and watch the modern container preview change.

Frontend

modern-web

API

modern-api

Database

modern-postgres

Namespace

modern-workloads

live database terminal
ready
db@modern$

terminal output

live response
db@modern$ modern db recent
Loading the modern workload activity feed...

01

Connect

Reach the VCF frontend, API, and PostgreSQL shell that anchors the lane.

02

Readback

Confirm the feed and preview reflect the fanout trigger.

03

Trigger

Insert one safe row that represents the fanout event.

04

Teardown

Leave the modern lane ready for another cross-cloud fanout cycle.