4 ms·
Pretty cool. Is there a write up on architecture and usage models? I’d like to see it. I was a happy couch 1.x user, but moved away with 2.0. Nothing specific
by deitcher 9y ago
Pretty cool. Is there a write up on architecture and usage models? I’d like to see it.
I was a happy couch 1.x user, but moved away with 2.0. Nothing specific about it, just needs and timing.
- ioquatix 9y agoThanks for being so interested. The architecture is super simple, I'd suggest that the first place to look is the source code. There are really only two ways of accessing the underlying data store - a read-only dataset and a read/write changeset which can be committed. It's purely a key-value storage at the core - a key being a path and a value being whatever you want. On top of that you can build more complex things, e.g. https://github.com/ioquatix/relaxo-model https://github.com/ioquatix/relaxo-model which provides relational object storage and basic indexes (e.g. has one, has many, etc)