Eventually consistent external materialized views.
(Note: Originally a fork of https://github.com/kirasystems/views)
Gered
5ec96d6db2
why do this? well, i think the biggest gain from the perspective of a developer looking to use this library is that this simplifies the use of it. it becomes easier to change things in this library (and also in others that plug into it, such as views-honeysql and other libraries providing alternate IView implementations) to have a much better out-of-the-box working configuration for the common use-cases. additionally, i could not think of a scenario where i would want to have more then one view-system hanging around given that you can plug in multiple different IView implementations into the same view-system that potentially each work with a different backing database. the big complaint i could see against this change is that it goes somewhat against a "functional approach" with the global state that is used automatically by the functions in the library. personally, i (right now) see it as a more _practical_ approach. and for me that wins out in the end. who knows, perhaps i will deeply regret this change down the road. |
||
|---|---|---|
| src/views | ||
| test/views | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| NOTES.md | ||
| project.clj | ||
| README.md | ||
views
Eventually consistent external materialized views.
Notice: library is still somewhat in flux.
Design
TODO
Usage
TODO
Testing
TODO
License
Copyright © 2015-2016 Kira Inc.
Authors Dave Della Costa (https://github.com/ddellacosta) and Alexander Hudek (https://github.com/akhudek)
Distributed under the MIT License.