Challenges of distributed messaging systems

Go Time: Golang, Software Engineering

Distributed systems are hard. Building a distributed messaging system for these systems to communicate is even harder. In this episode, we unpack some of the challenges of building distributed messaging systems (like NATS), including how Go makes that easy and/or hard as applicable.

Join the discussion

Changelog++ members support our work, get closer to the metal, and make the ads disappear. Join today!

Sponsors:

• DigitalOcean – DigitalOcean’s developer cloud makes it simple to launch in the cloud and scale up as you grow. They have an intuitive control panel, predictable pricing, team accounts, worldwide availability with a 99.99% uptime SLA, and 24/7/365 world-class support to back that up. Get your $100 credit at do.co/changelog.
• Retool – Retool makes it super simple to build back-office apps in hours, not days. The tool is is built by engineers, explicitly for engineers. Learn more and try it for free at retool.com/changelog
• Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com.

Featuring:

• Derek Collison – GitHub, X
• Johnny Boursiquot – Website, GitHub, X
• Mat Ryer – Website, GitHub, LinkedIn, X
• Jon Calhoun – Website, GitHub, X

Show Notes:

• nats.go
• What is the definition of “cattle not pets”?
  
• Idempotence
• Apache Kafka

Something missing or broken? PRs welcome!