[hasante]

Hi - its not - more about 20% - for tests and non critical things.

Focusing on your abandonment part etc etc:

- Its not really trying to achieve that, this is simply a more efficient model, with a good storage coupling (for chat).

- What is being achieved here is a cohesive solution for chat specific workloads and optimising for it.

One of the benefits is speed (throughput, latency) - and very cheap calls.

More so - under sql, and for developers who have different demands and mostly changing demands - the effort is quite complicated situation (I speak from my own experience)

The focus here is a simple downmost layer - that allow all the varieties of top layers & requirements to be achieved easily.

In my blog post - i share a variety of these.

Also product is not ready - but thought i share this idea - as i think it can be of benefit to most devs who are starting out with a product.

You technically dont even need progressdb to achieve it - You can do it with a backend based pebble or rocksdb database.