Hacker News Reader

I see that the pricing model has changed from flat-rate to per-GB. Much more interesting to work now, although still on the high-end (but nice that there's no further charge for queries). The previous comparison to a Postgres instance using JSONB still stands.

How do query times scale with data size? Also is there any full-text search (other than regex)? That would make it more compelling.

View on HN

Full-text search related functions can be found here: https://docs.rockset.com/text-search-functions/

As the data grows, we manage shards under the hood to ensure that the data spread across more nodes which in turn helps us use more parallelism. It is possible to manage the query performance and the data size independently in our architecture. Look out for numbers in a future blog post.

and 100KB/s is the max ingest rate?

That's just for streaming input by default. We do work with users and can increase it if the use-case demands it. For bulk ingest from sources like S3, that limit does not apply and it typically does many MB/s.

(I work on the product team at Rockset.)

Reply on news.ycombinator.com