# Request for Comments: CRDTish approach to Solid **URL:** \ **Category:** Build a Solid App\ **Created:** [April 10, 2021, 8:01am UTC](https://forum.solidproject.org/t/request-for-comments-crdtish-approach-to-solid/4211 "2021-04-10T08:01:34Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![aschrijver](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/aschrijver/32/463_2.png) [@aschrijver](https://forum.solidproject.org/u/aschrijver)\ **Post date:** [April 12, 2021, 10:15am UTC](https://forum.solidproject.org/t/request-for-comments-crdtish-approach-to-solid/4211/7 "2021-04-12T10:15:22Z")
> [@NoelDeMartin](#): > > (I also read about it in [this forum](http://forum.solidproject.org/t/application-of-crdts-to-solid/3321) a while ago). In that thread @pukkamustard [mentions](http://forum.solidproject.org/t/application-of-crdts-to-solid/3321/14) Distributed Mutable Containers. Just wanted to add to that this DMC spec has been progressing a lot since then, and now lives at different locations: - [DREAM enables Group P2P Collaboration](http://dream.public.cat/pub/dream-data-spec) - [http://purl.org/dmc](http://purl.org/dmc) > [@Vincent](#): > > Other terms that you might be interested in researching are **event sourcing** / **command query responsibility segregation (CQRS)**. Very interested in these myself. In combination with Domain-Driven Design (DDD), which maps well to closed Linked Data vocabularies (acting as bounded contexts to model a particular business domain), and is a very good way to take non-technical folks along a software-design process, up to testable and very modular, maintainable codebases. (Note, the Event Sourcing is optional. You see it used in many examples, but it adds a lot of complexity in form of eventual consistency issues and code that is harder to test. You can always start with CQRS and extend to ES later on) --- _[View the full topic](https://forum.solidproject.org/t/request-for-comments-crdtish-approach-to-solid/4211)._