What problems is QuestDB solving and how is that benefiting you?
Persisting and analysing/querying large sets of sensor data from various PLC machines.
At a client we have a setup with various PLC machines with different sensors attached. We sample data of some 100-300 variables at rates of 500Hz to 1kHz.
Initially we tried other solutions with bad performance due to the varying datasets. Other solutions struggled with performance when the datamodel got updated (added or removed sensors).
With QuestDB we managed to easily deploy a setup where ingesting this type of data was no problem. We went with small edge-deployed servers dealing with single PLC and a two larger QuestDB instances where one was used to aggregate data for all PLC's to facilitate any near-realtime queries of status of all PLC's and the other larger instance was used to persist data-sets that was classified as valuable to keep for long term analysis.
Having the http/rest-api allowing ingestion and queries simplifies integration with other systems of ours without the need to link to specific database libraries.
The built-in UI that houses query capabilities among others allow us to run quick tests and concepts and in recent releases this also hints at bad server configurations and how to fix some bad server configuration to get the best QuestDB experience.
As a developer I have really enjoyed the open and welcoming attitude by the QuestDB developers. They have actively listened and implemented a lot of end-user suggestions. Review collected by and hosted on G2.com.