Architecture: NATS

A microservice publishes an order event. Three other services need to know about it: inventory has to decrement stock, billing has to charge the card, and shipping has to queue a label. In a lot of systems, that fan-out means standing up a broker, provisioning disks, tuning partitions, and running a coordination service alongside it. Then you check the memory footprint and realize the messaging layer is heavier than the services it connects. NATS … Read More

Explained: Chaos Engineering

It's 2 a.m. Your on-call phone goes off. A payment service is down, and nobody can explain why. It worked fine in staging. It passed every test. But somewhere in the tangle of microservices, a database connection pool quietly exhausted itself, and the fallback that was supposed to kick in never did. Nobody knew the fallback was broken. It had never been tested in production. Not once. This is the failure mode that chaos engineering was built … Read More