JWT for authentication
The API stays stateless, so any instance can serve any request without a shared session store.
CostRevoking a token before it expires needs extra work, because no server holds the session.
KyoMel / Yogyakarta, Indonesia
Case 0404 / 04
A contest management API with authentication, submissions, and an admin dashboard.
Problem
A contest needs one place to take submissions and one place to review them. Without it, entries arrive by email and the organiser tracks them by hand.
Decisions 2
The API stays stateless, so any instance can serve any request without a shared session store.
CostRevoking a token before it expires needs extra work, because no server holds the session.
Submissions are relational data with real constraints, so the database enforces them.
CostSchema changes need migrations, which is slower than a schemaless store.
Outcome
Next