Ctrl Alt Solve

Case studyJul 15, 2026·1 entry

a monolith endpoint without a big-bang rewrite

We extracted one high-churn billing endpoint behind a strangler facade. Dual-writes ran for two weeks while we compared totals nightly. A feature flag controlled read traffic so we could roll back instantly. The hardest part was matching edge-case rounding in legacy invoices. Cutover finished with no customer-facing downtime and a smaller blast radius. We kept the facade until three more endpoints followed the same path.

347 views0 likes0 comments0 bookmarks

#migration #billing #architecture

LLaura Petrova Read →

ComparisonJul 14, 2026·1 entry

vs Postgres for short-lived job locks

We needed locks so queue workers did not process the same job twice. Redis SET NX was faster under load and easy to expire automatically. Postgres advisory locks were simpler operationally for our small team. Failover behavior mattered more than raw latency in our case. We chose Postgres first, then moved hot paths to Redis later. Pick the lock store you can operate confidently at 3am.

336 views0 likes0 comments0 bookmarks

#queues #postgres #redis

Laura Petrova

Laura Petrova

Experiences shared

a monolith endpoint without a big-bang rewrite

vs Postgres for short-lived job locks