Flux/CQRS patterns for JavaScript application.
Write code thinking :)
Now, We can implement web application with Flux or Redux etc...
But, I often hear the story that is "Control flow of Flux/Redux is cool, but where to implement domain logic."
I think that the people skip to Flux/Redux from MV* pattern.
MV* --> ( HOLE ) --> Flux/Redux(CQRS+EventSourcing)
Almin.js aim to fill the HOLE between MV* and Flux/Redux.
Almin provide some pattern, is not framework.
- Testable
- Scalable
- Responsibility Layers patten - well-known as DDD(Domain-Driven Design)/CQRS
Almin is a implementation of Read/Write Stack Architecture that is well-known as Flux/CQRS.
npm install almin
📝 Please See Documents of Almin.
- Documents
- Tutorial
- Write usage instructions
- Implement flow
- UseCase
- Domain
- Repository
- Store
- State
- example/counter
- Simple Counter example
- It use only state
- example/todomvc
- Todo list example
- example/svg-feeling
- Separate Domain and Store/State
- Two way update state.
- How to implement for 60 FPS
- Component should implement
shouldComponentUpdate()
- Component should implement
- Separate Domain and Store/State
- example/shopping-cart
- Shopping Cart is a complex example.
- This example is implemented of flux-comparison.
- How to test.
- How to implement domain layer.
npm test
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature
- Commit your changes:
git commit -am 'Add some feature'
- Push to the branch:
git push origin my-new-feature
- Submit a pull request :D
MIT