Dulan Wirajith Lokunarangodage

How we fixed a 54-second clock skew bug in our auction platform using NTP-inspired calibration, zero backend changes, and five lines of math.

Health checks passed. PM2 was online. SSL was valid. Yet every request returned 500. How a crashing Nginx worker hid behind a perfectly healthy application.

Why Redis and not Kafka? Why Fargate and not Kubernetes? And what happened in staging that nearly derailed the entire migration? The honest debrief, tradeoffs, the mistake that almost broke production, and the final results.

Most Australian companies waste 30% on AWS. Learn real cost-cutting strategies from Sydney startups. Complete guide with code and metrics.

Building a reliable system means planning for failure, not just success. Here's how we engineered Multi-AZ failover, sub-30-second crash recovery, and observability that turned hour-long incidents into 10-minute fixes.

The core challenge of scaling Socket.IO is that each server instance is an isolated island. Here's how we used @socket.io/redis-adapter and the Socket.IO v4 upgrade to bridge those islands into one unified real-time system.

The real-world engineering decisions behind scalable systems-consistency vs availability, monolith vs microservices, sync vs async.

After the production outage, we had a clear mandate: no more single points of failure. Here's the new distributed architecture we designed, from ALB through ECS Fargate to Redis, and why we made each choice.

Real-world cloud cost optimization strategies applied to a production AWS environment-without sacrificing performance or reliability.

How production systems handle 100K+ concurrent users without degrading latency or reliability.

A traffic spike brought down our entire real-time platform without warning. Here's the story of what broke, why it broke, and the architectural decisions that followed.