sourced
sourced-repo-mongo
Our great sponsors
| sourced | sourced-repo-mongo | |
|---|---|---|
| 1 | 1 | |
| 284 | 55 | |
| - | - | |
| 1.8 | 0.0 | |
| over 2 years ago | about 1 month ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sourced
-
has anyone done a unit/integration testing in a class based nodeJS application?
https://github.com/mateodelnorte/sourced/blob/master/__tests__/entity.js https://github.com/patrickleet/circuit-breaker-await-async
sourced-repo-mongo
-
Problem with Repository Design Pattern
This is an event sourcing library in Typescript that also relies on the repository pattern: https://github.com/cloudnativeentrepreneur/sourced. Using the same models you could use a server side repo, such as https://github.com/CloudNativeEntrepreneur/sourced-repo-typeorm to persist to sql dbs, or the mongo repo implementation: https://github.com/mateodelnorte/sourced-repo-mongo, or even use localstorage if you were working in a browser: https://github.com/CloudNativeEntrepreneur/sourced-repo-svelte-local-storage-store all without changing the model the repository serves.
What are some alternatives?
mongo-event-sourcing - An open-source fully configurable and extendible tool that enables event sourcing in MongoDB.
segmentation_models.pytorch - Segmentation models with pretrained backbones. PyTorch.
sourced-repo-typeorm - A sourced repo that uses TypeORM to persist events. This allows for passing different connection options, and thus, allows for different databases for the persistence layers.
git-meta - Repository for the git-meta project -- build your own monorepo using Git submodules
sourced-repo-svelte-local-storage-store - Build event sourced svelte applications and use localstorage backed svelte stores for persistence.
meta - tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo?