Resolve the Quota Double-Spend: Design Meterly's Order-Provisioning Schema
Overview
What this challenge is about.
Resolve the Quota Double-Spend: Design Meterly's Order-Provisioning Schema. Advanced challenge in design. Designing real products under real constraints, ear...
The Brief
What you'll do, and what you'll demonstrate.
Design a PostgreSQL transactional schema and isolation-level strategy for Meterly's quota provisioning that enforces non-negative balances and bounded refunds, with tests proving the invariants hold under eight-way concurrency.
This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
Earning criteria — what you'll demonstrate
- Translate a documented production incident into precise, testable database invariants
- Select transaction isolation levels by mapping each candidate level to the specific concurrency anomaly it permits or prevents
- Apply explicit row-level locking and serializable strategies to eliminate lost-update and double-refund races
- Build randomized concurrency tests that distinguish a flawed schema from a correct one under parallel load
- Communicate isolation-level trade-offs clearly enough for another engineer to extend the system safely
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Transactions
Apply transactions to solve real industry problems and demonstrate production-level capability.
- Acid
Apply acid to solve real industry problems and demonstrate production-level capability.
- Isolation Levels
Apply isolation levels to solve real industry problems and demonstrate production-level capability.
- Postgresql
Apply postgresql to solve real industry problems and demonstrate production-level capability.
- Concurrency Testing
Apply concurrency testing to solve real industry problems and demonstrate production-level capability.
- Schema Design
Apply schema design to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Database Administrator
Owning a billing-grade ledger demands exactly the transaction and isolation skills this challenge exercises: you leave able to design schemas whose invariants survive concurrent load, the daily reality of a DBA guarding money-of-record data in production.
This challenge sharpens
- transactions
- isolation-levels
- schema-design
Backend Engineer (Data-Intensive Systems)
Backend engineers on payment and provisioning paths must reason about ACID guarantees and prove correctness under parallelism. This challenge bridges directly into that work by having you build and test the critical transactional paths a service relies on.
This challenge sharpens
- acid
- concurrency-testing
- postgresql
Site Reliability Engineer
Reproducing a documented incident, closing the race, and proving it stays closed under load is core SRE practice. You finish able to turn a postmortem into invariants and a regression-proof concurrency test, the skills that keep ledgers reliable.
This challenge sharpens
- concurrency-testing
- transactions
- isolation-levels