While working on the integration of a complex distributed task queue in a design-by-committee meeting, I wondered out loud why we parse AMQP messages more or less directly instead of using higher-level abstractions like Spring Integration or Celery.
A colleague argued that it wasn't a problem, and also it would be easy to integrate multiple languages, and the target programming languages would be able to handle everything just fine.
I begged to differ and pushed the whole thing up a notch: "technically, one could even parse AMQP messages in assembly if one were inclined to".
So long story short: this project was born as proof that low-level messaging integration is possible, even close to bare metal. Because who wouldn't need that?
- The producer and consumer ./amqp.asm communicate via AMQP messages,
- Docker Compose or Kubernetes (in the k3s incarnation) to orchestrate everything easily.
Two ways to start it: Docker or Kubernetes
Who doesn't run their assembly programs in Kubernetes? This way processes won't annoy you with their speed, and... when they crash!
So, fire up the cluster:
bash deploy.shIf you need a container registry to run it, check out: setup-k3s-with-registry.sh
If you'd rather see some output printed to your console, just start Docker Compose:
docker compose up --buildHave fun exploring the wild side of AMQP!