thema

Regarding the growing log in CRDTs, it doesn't have to be that way. Most of these popular CRDT libs use Merkle DAG only to build up the log of the changes. But there is a better way, you can combine a Merkle DAG for ordering + prolly trees for storing the actual state of the data. That gives you total ordering, an easy way to prune old data when you choose to, and an easy way to sync. Look into fireproof for how this is combined. Regarding distributed schemas, I agree, there's a lot of complexity there but it's worth looking into projects like https://www.inkandswitch.com/cambria/ and https://github.com/grafana/thema, which try to solve the problem. It's a young space though. If anyone else knows about similar projects or efforts, please let me know. Very interested in the space.

You may be thinking of the https://github.com/grafana/thema library, which is the extracted version from some other projects / internal tooling.

What is this 2 releases per feature you speak of? Can feature flags solve this? or maybe Thema (in time) https://github.com/grafana/thema

I've been thinking about this from a slightly different angle (https://github.com/hofstadter-io/hof), but I think we are both getting at a higher level of reuse and dependency management. I just don't think we need to limit the idea to APIs, there are different granularities, both bigger and smaller, where the ideas are useful. You might also find the Thema project by Grafana interesting (https://github.com/grafana/thema)