ShoalStack is now

platform201
Deploy a queue-backed order pipeline in GCP.

Order Queue Blueprint

This blueprint includes a producer, a consumer, a Gateway, a message queue, and a PostgreSQL database for building order pipelines that stay responsive while writes catch up.

About the Order Queue Blueprint

This blueprint provides a working e-commerce checkout and delivery pipeline that accepts orders quickly, processes them asynchronously, tracks status in real time, and provides a live delivery dashboard.

Use this blueprint as:

  • A queue-backed order pipeline
  • A starting point for producer and consumer services
  • A foundation for event-driven applications
  • A template for high-throughput write paths
Order Queue blueprint card: producer, consumer and dashboard
Delivery Dashboard container routed through the Gateway

How the Graph Works

This blueprint combines a Gateway, a message queue, three containers, and a PostgreSQL database that are already connected and configured, giving you a complete event-driven architecture that can be customized for your own services and workflows. platform201 deploys every component into a GCP solution and wires the services to the queue and the database.

Gateway

Routes incoming dashboard and API traffic to the correct container behind a shared public endpoint.

Delivery Dashboard

Displays order and delivery status in real time, serving the frontend where orders are placed and tracked.

Order Service

Receives and validates incoming orders, placing each one onto the queue immediately to keep API response times fast.

Message Queue

Buffers orders for reliable asynchronous processing, holding messages on the topic until the consumer is ready.

Order Collector

Consumes queued orders in the background, writes each record to PostgreSQL, and serves status back to the dashboard.

PostgreSQL

Stores processed orders and delivery state in a persistent database that updates out of band as messages arrive.

Order Service and Order Collector containers connected through the Message Queue to NeonDB

What You Can Build with This Blueprint

Use the Order Queue blueprint to build order pipelines, event-driven services, or applications that keep accepting requests while the writes behind them catch up.

Checkout Pipeline

Checkout Pipeline

Accept orders quickly and persist them from a separate worker.

Event-Driven Services

Event-Driven Services

Publish an event once and let independent consumers react to it.

Traffic Spike Absorption

Traffic Spike Absorption

Hold bursts in the queue instead of pushing them at the database.

Background Processing

Background Processing

Move slow work off the request path and into a background worker.

Booking & Reservations

Booking & Reservations

Record bookings and transactions without blocking the customer.

Audit & Activity Logs

Audit & Activity Logs

Capture each action as a message and write it down in order.

Using The Order Queue Blueprint

Move from code to a running backend with a visual setup flow that keeps services, connections, and deployment easier to manage.

1

Create a New Project

Create a new project in platform201 to get started.

2

Browse Blueprints

Open your environment and select Browse Blueprints to view available deployment templates.

3

Select the Blueprint

Choose the Order Queue blueprint to automatically generate the required components and connections.

4

Configure the Database

Configure and select an existing PostgreSQL database or create a new one. The DATABASE_URL environment variable will be automatically populated at container build.

5

Configure the Queue

Set how long the topic retains a message and configure the subscription for the consumer.

6

Set the Gateway Domain

Choose the domain your users will hit. The Gateway routes traffic to the producer, consumer, and dashboard.

7

Deploy

Click Deploy and let platform201 handle the cloud configuration, networking, and service wiring.

8

Submit Orders & Track Status

Open the dashboard, submit an order, and watch it process through the queue into PostgreSQL in real time.

After Deployment

Once deployed, platform201 provisions the Gateway domain, creates the topic and its subscription, and connects all three services to the queue and the PostgreSQL database they share.

You can immediately test the delivery flow using the open-source example from the platform201 message queue demo, or customize it with your own producer and consumer logic.

An order accepted by the worker, passed through the queue and stored in PostgreSQL

Ready to Deploy Your Order Pipeline?

Start with a working order pipeline, swap in your own producer and consumer, and deploy a queue-backed architecture without manually configuring Google Cloud infrastructure.

Deploy This Blueprint