Replace D-Bus with plain HTTP
|Target version:||Current Sprint|
In preparation of replacing dbus with redis we first need to find the right way to add
- Choose the right Redis module to use (most likely
- Package the module so our containers can use it
- Add a message passing module that provides a similar abstraction layer to how we use dbus currently
- Provide a simple way to start a redis server for tests (just like Postgres)
After it turned out that the resource allocator could just be removed without adding a replacement, i started to wonder if that might be the case for all our current uses of dbus. While it's not quite as straight forward for the websocket server and scheduler, there might be better options than using redis. I'm currently exploring the use of postgres pub/sub and/or plain HTTP as a replacement for dbus rpc. This might take a little time to figure out due to my limited understanding of the big picture, but the much simpler overall architecture should be worth it.