Design a Transactional Schema for a SaaS Order-Provisioning System
Overview
What this challenge is about.
Design the schema for orders, quota packs, consumption events, and refunds. Define each critical transaction (buy, consume, refund) with isolation level and locking strategy. Identify the invariants (e.g. balance never negative, refunds never exceed payments). Prototype on PostgreSQL. Write a test suite using pg_jepsen-style randomized concurrency tests that proves the invariants hold under 8-way concurrent load. Deliver the schema, transaction documentation, the test suite, and a 6-page design memo on isolation-level choices.
The Brief
What you'll do, and what you'll demonstrate.
Design a PostgreSQL transactional schema and isolation-level strategy for SaaS quota provisioning, with tests proving invariants hold under 8-way concurrency.
Earning criteria — what you'll demonstrate
- Reason about ACID and isolation levels for real money-flow transactions
- Choose between SERIALIZABLE and REPEATABLE READ with justification
- Write randomized concurrency tests that catch real bugs
- Defend isolation choices in a written design memo
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.