Skip to main content
AI Learning Resources

Quick Overview

In this technical conversation, Google Cloud developer marketer Tilde Thurium interviews Andrew Baker, VP of DevRel at Temporal. The discussion covers the architectural design and deployment of IMAXxing, a viral movie seat monitoring application. The project was built to demonstrate durable execution and serverless orchestration using Temporal and Google Cloud Run.

Key Points

  • 1.IMAXxing is an automated notification service built to monitor 70mm IMAX seat availability across the country for Christopher Nolan's The Odyssey.
  • 2.The application architecture uses Temporal for durable workflow orchestration and Google Cloud Run for running serverless worker capacity.
  • 3.Temporal workflows track user subscriptions as individual entity workflows and use signal events and timers to batch alerts and prevent excessive notifications.
  • 4.Using serverless workers with Temporal allows the system to scale compute resources directly according to task queue demand during sudden booking spikes.
  • 5.AI coding agents and tools like Terraform and the gcloud CLI significantly accelerated the infrastructure deployment and monitoring configuration.

Summary

Andrew Baker, VP of DevRel at Temporal, created IMAXxing as an automated seat-alerting system after 150,000 people bought tickets to initial 70mm IMAX screenings of Christopher Nolan's The Odyssey. Recognizing that moviegoers frequently cancel or change their plans, Baker designed the platform to continuously monitor theater seat maps nationwide. The application filters seat arrangements based on user preferences, ignoring poor viewing locations like the front row and identifying grouped seats for parties of varying sizes.

The core architecture couples Temporal with Google Cloud Run to provide durable execution and resilient failure recovery. Baker implemented an entity workflow model where each user subscription runs as its own persistent workflow. A separate fleet of monitoring workflows tracks showings across all supported theaters. When an open seat is discovered, the monitoring workflow sends a signal to matching subscription workflows. To avoid overwhelming subscribers with multiple notifications within a short window, the subscription workflow starts a one-minute timer upon receiving an availability signal, collecting subsequent openings before authoring and dispatching a single consolidated email or Telegram alert.

Running Temporal workers as serverless workloads on Cloud Run resolves the challenges associated with managing spiky background processing. Traditional always-on worker models often force developers to over-provision static compute resources to survive unexpected traffic spikes. With Temporal serverless workers deployed on Cloud Run, worker capacity scales automatically in response to Temporal task queue demand rather than secondary CPU metrics. When no tasks are pending, the workers scale down to zero, and when seat openings trigger thousands of concurrent workflow events, compute pools instantly expand to process matching logic and dispatch notifications.

Baker demonstrated live production dashboards in Grafana and Temporal Cloud, showing over 8,000 total user configurations and thousands of concurrently running subscription workflows. Running the service cost approximately a couple hundred dollars per month despite continuous national seat scraping and matching calculations. Baker highlighted how frontier AI coding agents accelerated the deployment lifecycle, generating Terraform configurations and Google Cloud CLI commands to establish the entire observability and hosting infrastructure rapidly.

Origin and purpose of IMAXxing

Andrew Baker created IMAXxing to help moviegoers find desirable seats for 70mm IMAX screenings of Christopher Nolan's The Odyssey after 150,000 opening tickets sold out quickly. The site monitors theater seating maps across the United States, filters out low quality front row seats, and alerts subscribers when matching open seats become available.

Workflow orchestration with Temporal

The application stack relies on Temporal to achieve durable execution across unreliable upstream theater APIs. Using an entity workflow model, each user subscription is represented by a dedicated workflow that receives signals from seat-monitoring workflows, pauses with a sixty-second timer to batch multiple theater updates, and dispatches consolidated email or Telegram notifications.

Deployment and serverless workers on Cloud Run

The compute infrastructure runs on Google Cloud Run using Temporal serverless workers. Instead of maintaining over-provisioned, always-on worker pools to handle sudden demand spikes, the system scales compute capacity up and down dynamically based on Temporal task queue backlog.

Operational scaling, costs, and AI tooling

The service scaled to over 8,000 subscribed configurations and several thousand active workflows at an operational cost of a couple hundred dollars per month. Baker used AI coding agents alongside Terraform and Google Cloud CLI tools to rapidly scaffold and deploy the production infrastructure and Grafana monitoring dashboards.

The Bottom Line

The video establishes how combining Temporal durable execution with Google Cloud Run serverless workers enables a resilient, auto-scaling notification service capable of managing spiky workloads at minimal operating cost. It demonstrates the implementation of entity workflows, batched signaling, and AI-assisted cloud infrastructure setup. The discussion concludes by showing that serverless worker orchestration effectively eliminates the need for expensive, over-provisioned worker pools in event-driven systems.

FAQ

What is IMAXxing and how does the ticket alerting application work?

IMAXxing is a notification application that monitors 70mm IMAX seat maps across the country for The Odyssey. It tracks theater availability, matches newly opened seats against subscriber party sizes and viewing preferences, and dispatches email and Telegram alerts.

How does Temporal provide durable execution for the IMAXxing application stack?

Temporal guarantees durable execution by preserving workflow state across key transition points and retrying failures automatically. This ensures operations survive downstream API outages and transient infrastructure errors without dropping user alerts.

Why does the IMAXxing subscription workflow implement a one minute timer?

The workflow sets a sixty-second timer after receiving an initial availability signal to batch multiple updates together. This prevents sending noisy back-to-back notifications if several seats open up across different theaters within a few minutes.

How do Temporal serverless workers on Google Cloud Run handle workload spikes?

Serverless workers dynamically scale compute capacity up and down based directly on the number of pending tasks in Temporal queues, rather than relying on imprecise metrics like CPU utilization. This avoids paying for idle, over-provisioned worker instances while accommodating sudden traffic surges.

How were AI coding agents used during the construction of IMAXxing?

AI coding agents assisted with generating Terraform infrastructure configurations, executing Google Cloud CLI commands, and setting up Grafana monitoring dashboards for production operations.

Worth watching for

Software engineers and cloud architects interested in building resilient event-driven systems using Temporal workflows and Google Cloud Run.

  • temporal
  • google-cloud-run
  • serverless
  • architecture
  • cloud-computing
Watch on YouTubeMore videos from Google Cloud Tech