| Sorry to hear about your painful past experience and thanks for sharing this feedback. QuestDB improved a lot in the past two years and it's much more robust and production-ready now. A couple of things the engineering team did to address this as it grew from the early days at Ycombinator: QuestDB introduced fuzz tests for all major database components [1] which helped find and fix lots of bugs. Besides that, the SQLancer team [2] was kind enough to add QuestDB support and find bugs around tricky SQL edge cases. We do our best to squash all critical bugs and constantly grow our integration tests suite. On the SQL side specifically, we brought many SQL-related fixes over the last few years, introduced EXPLAIN and query plan testing, and finally improved memory management of cached queries. We're prioritising new bugs should they arise on GitHub or elsewhere. Large companies such as Airtel [3], Mizuho Bank, Airbus, NetApp, Yahoo [4], Central Group [5] (largest retailer in Asia), Cloudera use QuestDB in production today. There is still a lot of work to be done to bring better functionality. If you're keen to try QuestDB for one of your projects, we'd love to hear your feedback and see how it works for you. [1] https://questdb.io/blog/fuzz-testing-questdb/
[2] https://github.com/sqlancer/sqlancer/
[3] https://questdb.io/case-study/airtel-xstream-play/
[4] https://questdb.io/case-study/yahoo/
[5] https://questdb.io/case-study/central-group/ |