undefined | Better HN

0 pointsmanigandham7y ago0 comments

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.

0 comments

canadi7y ago

add_docs() API always UPSERTS and so yes, updates are through "_id". The system auto-assigns an "_id" only when it is not supplied by the user or when an existing field is not mapped as the "_id" field at collection creation time. You will have to use delete_docs() before add_docs(), if you want replace-document behavior.

Our backend architecture is quite scalable and actually grows and shrinks with the demand continuously.

And yes, all documents are automatically indexed and replicated for fast query performance, which is more expensive than just storing them in "_id"->"doc" format. For our use cases and value prop, this one time indexing cost pays for itself several times over by saving time during query processing.

j / k navigate · click thread line to collapse

0 pointsmanigandham7y ago0 comments

Interesting use-case for prototyping but I don't see how it is cost-effective for higher-scale usages. Congrats on the launch though.

0 comments

canadi7y ago

Our backend architecture is quite scalable and actually grows and shrinks with the demand continuously.

j / k navigate · click thread line to collapse