Apache IoTDB vs Gravity Forms

IoTDB 2.x has reached a level of SQL completeness — set operations, CTEs, window functions, JOIN variants, MATCH RECOGNIZE, and now logical views — that makes it viable for data engineers who previously had to export time-series data into a relational database for complex analysis. The 1.3.x branch is in maintenance mode, receiving only security backports. The AINode capability adds built-in ML models (Timer-XL, Timer-Sundial) for in-database forecasting.

The 2.x line is systematically adding relational SQL expressiveness atop the IoT-native storage core, adding 2-4 SQL features per release. The C-language SDK signals an intent to expand beyond JVM-centric deployments into embedded and industrial control contexts. AINode points toward a longer arc: time-series forecasting and anomaly detection executed directly in the database, reducing the need to export data to Python for ML workflows.

The next releases will likely complete table model SQL parity with standard features still missing, and expand AINode inference to cover more model types or expose forecasting via standard SQL function syntax.