
Single-server WebSocket worked in dev. Production with load balancers? Redis pub/sub saved the day.
WebSockets are easy to set up. Scaling them? That's a different story.
When I built Drawsheet and Connect, single-server WebSocket worked fine in dev. But in production with multiple instances behind a load balancer, messages stopped reaching the right clients.
I added Redis pub/sub between WebSocket servers. When a message comes in on Server A, it publishes to Redis. Server B subscribes and forwards to its connected clients.
Real-time is addictive once you get it right.

After trying Lerna, Nx, and plain workspaces — Turborepo changed everything with zero-config caching and parallel execution.

I've used both in production. Prisma for rapid prototyping, Drizzle when performance matters.

One docker-compose up and everything works. Database, Redis, backend, frontend. Your teammates will thank you.

Migrated from Pages Router to App Router. Server components are a game-changer but the learning curve is real.

Cache-aside, write-through, TTL strategies — practical patterns I use in production every day.

From zero to automated deployments. How I set up lint, test, build, and deploy pipelines for every project.

Discriminated unions, template literals, satisfies operator, and more. Level up your TS game.

Access tokens, refresh tokens, rotation strategies. Stop storing JWTs in localStorage.

Indexes, query plans, connection pooling, and EXPLAIN ANALYZE. Make your queries fly.