Comments (2)
As I am with you with most of ideas and like them, this one I don't agree. CosmoStore always had one and only goal - just be solid event store for F# (initialy only for Cosmos DB). It is not meant to be swiss knife for event sourcing. The reason here is that every devs has own opinion about how should projections / aggregates look like and what is the best approach.
I don't want to force anyone (even on passive level) to use Aggregate type as I described in my blog post. I mean... I still like it, but there will be probably another topic regarding versioning, where every change in Aggregate should be versioned so there is no just one Aggregate, but there are more of them depending when you want to apply events (like for example tax laws - each year different rules and you must apply events in respect to when did it happen). So it's getting more and more complicated and goes way beyond scope of simple event store for F#.
I love how you want to help others stepping into event sourcing (really!), but I don't think it belongs here. Maybe starting another project aiming to be swiss knife for event sourcing? I'd love to see something like that.
from cosmostore.
Got your point. Agree with it...
from cosmostore.
Related Issues (20)
- Document with type=Stream HOT 5
- Collection name cannot be specified? HOT 4
- ESERROR_POSITION_POSITIONNOTMATCH return last position? HOT 1
- Version 3 discussion HOT 42
- In memory example configuration HOT 8
- Confusion in types. Might need some extra functions. HOT 6
- Should we have read me for all stores ? HOT 3
- We should have github actions to push to do all the CI / CD. HOT 2
- There is some Dependancy issues HOT 1
- Missing Version in CosmoStore 3.0? HOT 7
- Dapper implementation for CosmoStore
- MongoDB implementation for CosmoStore
- CouchDB/ Cloudant / Couchbase implementation for CosmoStore.
- Azure TableStorage from connectionstring
- CosmosDB ChangeFeed - Read Document as EventRead outside of CosmosDB EventStore
- Observing appended events on distributed systems HOT 7
- Azure Table Storage requires JToken payload HOT 1
- One or more errors occurred. (unordered field Item) - This is probably more a question. HOT 13
- Switching to Azure.Data.Tables HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cosmostore.