Hi @ashn !
Thanks for stopping by the booth. Yah, those questions came in during my demo around 11am!
Here’s how real-time updates work on Rockset
Rockset makes it possible to provide low latency and high write rates with RocksDB-Cloud and remote compaction. Developers also save on compute and I/O with incremental indexing using the Patch API. Overall, real-time insights with millisecond query latency allow applications to move faster.
To elaborate more on the PATCH API:
The PATCH API solves the problem that other databases have with re-indexing the whole document. At Rockset, we use the PATCH API to incrementally index the collection. This means that for any updates that a collection gets, only part of those fields in a document are reindexed while keeping the rest of the fields in that document untouched. This means we are efficient in compute and i/o.
How converged index works and how’s that different from other databases
Converged Index = ROW + Column + Search.
We store every column of every document in a row-based store, column-based store, AND a search index.
Converged indexing requires more space on disk, but our queries are faster. We trade off storage for CPU. However, more importantly, we trade off hardware for human time. Humans no longer need to configure indexes, and humans no longer need to wait on slow queries. This is very different from other databases and such.
We also built a custom SQL query optimizer that analyzes every query and decides on the execution plan. For example, when to consider a columnar index vs. a search index.
I hope this helps answer your questions. Here are more resources to get you started:
Please let me know if you have more. I hope you had a great time at the conference!