CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.
I

Isabelle Dupont

@isabelledupont

API Engineer

0 followers1 following0 expertise score5 posts

OpenAPI-first services and developer experience that doesn't suck.

Node.jsGraphQLOpenAPI

Experiences shared

Case study5d ago·1 entry

broke in webhook delivery while rolling back payments

We ran into this around webhook delivery while rolling back payments. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.

0 views0 likes0 comments0 bookmarks
#webhook delivery
IIsabelle Dupont
Read →
Case study21d ago·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.

300 views0 likes0 comments0 bookmarks
#billing#migration#architecture
Isabelle Dupont
Comparison22d ago·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.

22 views0 likes0 comments0 bookmarks
#queues#postgres#redis
Isabelle Dupont
Discussion23d ago·1 entry

typed API clients reduce bugs more than OpenAPI docs?

Curious how teams balance generated clients and hand-written SDKs. OpenAPI docs help humans, but drift still sneaks into multi-repo setups. Generated clients catch breaking changes in CI before they hit prod. They can also create noisy diffs when schemas change often. Plain fetch wrappers stay flexible but hide contract mismatches. What has actually reduced production bugs on your teams?

378 views0 likes0 comments0 bookmarks
#api#typescript#dx
Isabelle Dupont
Recommendation24d ago·1 entry

for a practical observability stack for a 6-person team

We need traces and logs without hiring a full-time SRE. Right now we stitch screenshots from three tools during incidents. OpenTelemetry looks right, but the vendor choice is unclear. We ship weekly and cannot afford a six-month platform project. What has worked for small teams that still sleep at night? Especially interested in cost ceilings and onboarding time for juniors.

259 views0 likes0 comments0 bookmarks
#sre#opentelemetry#observability
Isabelle Dupont
I
Read →
I
Read →
I
Read →
I
Read →