/node
Posts touching node.
12 posts
- December 22, 2025 5 min
Building a fintech reconciliation engine that handles ten million transactions a day
PostgreSQL partitioned tables, Node.js worker pools, idempotent batch processing, and a custom diffing algorithm. Sub-minute reconciliation at ten million daily transactions.
- /fintech
- /financeops
- /postgres
- /architecture
- /node
- March 3, 2025 5 min
Postgres connection pooling: the problem you do not know you have until you have 50 concurrent users
Our Node.js API opened a new PostgreSQL connection per request. At 50 concurrent users we exhausted the connection limit and the whole system halted. PgBouncer fixed it.
- /postgres
- /architecture
- /node
- /financeops
- /blog
- January 20, 2025 5 min
Migrating from REST to a hybrid REST/event architecture without stopping the train
Our reconciliation engine needed async event processing but API consumers expected synchronous responses. The strangler fig pattern applied to a fintech data pipeline.
- /kafka
- /architecture
- /api-design
- /node
- /blog
- October 9, 2024 4 min
Next.js 15, Turbopack stable, and the mass codebase migration nobody is talking about
Next.js 15 shipped with Turbopack stable and async request APIs that break every existing middleware and dynamic page in your application.
- /react
- /node
- /typescript
- /architecture
- /blog
- September 25, 2024 4 min
The night our database ran out of connections and what I learned about pooling
At 2am our payment processing froze. Every database connection was consumed by long-running report queries sharing a pool with transactions.
- /postgres
- /node
- /architecture
- /fintech
- /experience
- August 28, 2024 3 min
Why every API endpoint at FinanceOps returns the same error shape
Our frontend had seven different error format handlers. I standardized every endpoint to return the same discriminated union error shape.
- /api-design
- /typescript
- /node
- /fintech
- /blog
- July 31, 2024 4 min
Docker multi-stage builds that actually make your images small
Our production Docker image was 1.2 GB. After an afternoon of optimization it was 89 MB. Here is the exact Dockerfile evolution.
- /docker
- /ci-cd
- /node
- /blog
- July 17, 2024 4 min
Why we picked React Server Components over a separate API layer
I tried React Server Components for our internal dashboard and realized I could eliminate the entire API serialization layer for read-heavy pages.
- /react
- /node
- /architecture
- /api-design
- /blog
- June 12, 2024 4 min
How I use PostgreSQL as a job queue and why you probably should too
Every guide says use Redis or BullMQ for background jobs. I used PostgreSQL SKIP LOCKED and it handled thousands of jobs per day with zero additional infrastructure.
- /postgres
- /node
- /architecture
- /fintech
- /blog
- May 29, 2024 4 min
Building a real-time notification system with zero external dependencies
We needed real-time payment notifications but could not justify Redis or a managed WebSocket service. SSE and PostgreSQL LISTEN/NOTIFY did the job.
- /node
- /react
- /api-design
- /architecture
- /blog
- May 22, 2024 4 min
Node.js 22 dropped and here is what actually matters for production backends
Node.js 22 shipped with require(esm) and a built-in WebSocket client. Here is what I benchmarked and what I adopted immediately.
- /node
- /typescript
- /architecture
- /blog
- April 10, 2024 4 min
Bootstrapping a Next.js monolith when everyone says microservices
I shipped our entire fintech platform as a single Next.js application. Here is why a monolith was the right call for a team of three.
- /react
- /node
- /architecture
- /startup-life
- /blog