Build an Application at Google Scale with Spanner, Cloud Foundry, and Google Cloud Platform
summary
Demonstrates a ticketing API built on Cloud Foundry spread across three CF regions behind Google Front Ends using a multicast IP so traffic routes to the lowest-latency region. Uses Google Cloud Spanner via the GCP Service Broker for strong ACID read‑write transactions that decrement seat counts safely under contention, drives concurrent buyers with preemptible GCP instances, and shows a live Spanner instance scaled from one to ten nodes, claiming single‑digit latencies and up to five nines availability.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:33Naive solutions for ticket sales
- 8:13Cloud native solution with Cloud Foundry
- 10:41Introducing Cloud Spanner
- 14:14Spanner transactional concepts
- 15:05Demo of ticket application
- 18:33Stress testing the system
- 23:51Global traffic routing with load balancer
- 25:33Querying Spanner data in console
- 27:50Getting started with Spanner today
- 28:53Future of Spanner and Q&A
related talks
21mCloud Foundry on Google Cloud Platform
37mGoogle Cloud Spanner: Going global with relational database
33mGoogle Cloud Spanner: Global consistency at scale
52mSpring to Google Cloud Native
47mGoogle Cloud Spanner: Global consistency at scale
04mLightning Talk: Google Cloud Data Services and Cloud Foundry
49mSpanner - fully managed horizontally scalable relational DB with ACID transactions
30mBuilding distributed systems is hard - case study (...)