The SQL with dot notation is nice, and something other databases have failed at doing with JSON. As for updates, it looks like _id is set automatically, and there's no UPDATE endpoint listed in the docs, so how is data mutated (by key)?
And my comment was more about the price, because at low volume of 10M records, any database system can already do fast queries. From the whitepaper, it looks like the indexing is intensive and that's where most of the cost is coming from, and explains the active/passive storage and tiered rocksdb-cloud setup.
Interesting use-case for prototyping but I don't see how it is cost-effective for higher-scale usages. Congrats on the launch though.
And my comment was more about the price, because at low volume of 10M records, any database system can already do fast queries. From the whitepaper, it looks like the indexing is intensive and that's where most of the cost is coming from, and explains the active/passive storage and tiered rocksdb-cloud setup.
Interesting use-case for prototyping but I don't see how it is cost-effective for higher-scale usages. Congrats on the launch though.