LavinMQ technical onboarding: background, stack & build

When developers join the LavinMQ team, they learn the technical basics from the people who built it. Sharing this onboarding opens the same knowledge to the wider developer community.

Key takeaways

LavinMQ started in 2017 as a spinoff from AMQProxy, a proxy built to combat connection churn. Today it is a high-performance, low-resource message broker developed by an experienced team at CloudAMQP.
LavinMQ is built with make. Each build target lists its dependencies and is rebuilt only when one of them changes. Make targets encapsulate the compiler flags used throughout the build.
In production, LavinMQ’s web UI is compiled into the binary, so deployment is a single file. During development, a separate frontend target with live reload lets developers change the UI without recompiling the server.

What part 1 covers

Where LavinMQ came from and why it exists
An overview of the technology stack
What LavinMQ looks like on disk: the data directory
How LavinMQ is configured
The binaries built, and how the build process works

Watch the full session

Posts in this series

Part 1: background, stack & build (this post)
Part 2: coming soon

Developers can continue the conversation on Slack and connect directly with the LavinMQ team.