Hi all, as you know I’m working on the more industrial use-cases for IoTDB … now I came across the IoTDB data-subscription feature and would like to propose creating a new component (I’m happy to do that).
I would like to try to use IoTDB as sort of a central instance for building a small MES system … here I need to be able to subscribe for various values and have some code called whenever these values change. Now I could use the thrift connector, however that would make me start one thrift server for every callback, assigning a free random port for each one and passing that information along with the registration. As I’m running everything inside the same VM this sort of sounds silly and a waste of resources. So, my idea was to create some sort of “InVmConnectorRegistry” where I can register clients which I give a unique name. In the connector config, I then simply use the “in-vm-connector” and pass along the connector name as an argument. Then IoTDB doesn’t have to do all the thrift connection handling, serialization, deserialization stuff. Does this make sense? If it does and I build such a thing, then it should be super easy to run subscription-based logic as soon as data changes in IoTDB, which would be a HUGE thing, I think. Chris
