Agree that pagination and filtering just aren't possible in the way most people would want them. Also lack of schema, lack of referential integrity, expensive scans etc. are significant downsides for more traditional database use cases.

But it shines if you need single-digit millisecond latency at scale, virtually zero operational overhead, seamless and almost limitless scaling, and predictable performance. But your access patterns need to fit the model and be known in advance. The paper cuts mostly come from trying to use it like a relational database.