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 assembler 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?
ctde•5h ago
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 assembler 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?