12 Calm Years of PostgreSQL in Critical Messaging
summary
PostgreSQL runs production critical messaging since 2000 for hospitals, EMS and fire, replacing a commercial RDBMS and later Sleepycat for routing; it handles 250,000 accounts, one million devices and per-message SLAs measured in seconds, routinely delivering large blasts in ~10s where cell takes minutes. Built systems include front-end dispatch, backend routing, throttling and per-minute RF event ingest for monitoring, use encrypted RAID, point‑in‑time snapshot replay for recovery, and after twelve years the stack proves reliable and operational.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 6:40Who am I
- 8:08My background
- 11:23What is critical messaging
- 13:07Oneway satellite
- 13:29Typical use cases
- 14:16Time to delivery
- 15:16Live support
- 18:17Web dispatching system
- 19:29Going live
- 24:35Time synchronization
- 27:47Routing
- 34:43Table Snapshot
- 35:20PostgreSQL Profile
- 37:22PostgreSQL Profile Diagram
- 44:31Unified Message Assembly
- 46:36SkyTell Network
- 52:05PostgreSQL Example
- 53:16Joes Books
- 53:48Low on Time
related talks
46mWhy PostgreSQL is becoming the standard in Financial Services
46mBig databases, many servers, data center or cloud - it's all here!
08mUsing PostgreSQL in real life
51mPostgreSQL at Pandora
23mPostgres as a Message Broker
54mBreakout Session
19mPostgreSQL Challenges
28mUsing a database in a data science project - Lessons learned in production