Ideas and todos

[janzenisek]

Sockets:

• check feasibility of IMessage, Message, Message
• check if blocking execution has any effect (compare kafka vs. mqtt)
• implement logging: e.g. using serilog
• implement SIDL file generation: implement message registration methods, reflect types, generate SIDL-code
• enable publishing with qos "consume exactly once": kafka: consumer groups, mqtt: implement worker queues at broker and/or socket side;
• implement (re-)connection handling: currently using kafka and mqtt inbuilt configs
• persistence idea: save and load sockets including all props e.g. from litedb; possible reasons: not everything can be loaded from config (e.g. queued jobs, subscribed actions).

Broker:

• mqtt: add logging (e.g. using serilog)
• kafka: check possibility to intercept
• kafka: implement router-client to simulate mqtt topic routing

DemoApp(s):

• implement socket-configuration: yml-configs -> config-object -> dependency injection based socket instantiation
• add computation intensive example