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