Event-driven systems

Go Time: Golang, Software Engineering

In this episode we talk with Daniel and Steve about their experience with event-driven systems and shed some light on what they are and who they might be for. We explore topics like the complexity of setting up an event-driven system, the need to embrace eventual consistency, useful tools for building event-driven systems, and more.

Join the discussion

Changelog++ members save 3 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Teleport – Quickly access any resource anywhere using a Unified Access Plane that consolidates access controls and auditing across all environments - infrastructure, applications, and data. Try Teleport today in the cloud, self-hosted, or open source at goteleport.com
• 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
• Linode – Get $100 in free credit to get started on Linode – Linode is our cloud of choice and the home of Changelog.com. Head to linode.com/changelog OR text CHANGELOG to 474747 to get instant access to that $100 in free credit.

Featuring:

• Daniel Selans – Website, GitHub, X
• Steve High – GitHub, X
• Jon Calhoun – Website, GitHub, X
• Kris Brandow – GitHub, X

Show Notes:

• Batch - Daniel’s company, which is a platform for working with message busses and event-driven systems.
• RabbitMQ - An event/message bus tool.
• MQTT - Another event/message bus option that is very simple.
• etcd - A fast key/value store. Daniel talks about using it as a cache in the episode.
• Plumber CLI - A tool written by Batch to help work with any message bus
• Event Sourcing - Martin Fowler’s article on event sourcing.
• CUE - An encoding tool mentioned in the episode.
• Code blocks example from Steve - In the show Steve mentions code blocks helping readability. This is an example of this.

Something missing or broken? PRs welcome!