add link to new `compound` library
This commit is contained in:
parent
aaae41a262
commit
b7e6b4b784
|
@ -6,11 +6,12 @@ bettering mirroring the structure in my server-side database?
|
|||
### Answer
|
||||
|
||||
These libraries might be interesting to you:
|
||||
- [compound](https://github.com/riverford/compound)
|
||||
- [SubGraph](https://github.com/vimsical/subgraph)
|
||||
- [pull](https://github.com/juxt/pull)
|
||||
|
||||
If you want to go whole hog and ditch `app-db` and embrace DataScript,
|
||||
then you'll find [re-posh](https://github.com/denistakeda/re-posh) interesting.
|
||||
then you might find [re-posh](https://github.com/denistakeda/re-posh) interesting.
|
||||
|
||||
|
||||
***
|
||||
|
|
|
@ -55,7 +55,7 @@ another you'll be using "Reagent + a broader architecture".
|
|||
|
||||
1. Events are cardinal. Nothing happens without an event.
|
||||
2. Events are data (which means they are loggable, and can be queued, etc).
|
||||
3. Events are handled async (A critical decision. Engineered to avoid some `core.async` issues!).
|
||||
3. Events are handled async (a critical decision. Engineered to avoid some `core.async` issues!).
|
||||
4. For efficiency, subscriptions (reactions) should be layered and de-duplicated.
|
||||
5. Views are never imperative or side effecting (best effort).
|
||||
6. Unidirectional data flow only, ever.
|
||||
|
|
Loading…
Reference in New Issue