Dimitar Nanov

Having what @adrai said in mind, there are a few patterns you can apply to solve your problem, after you have decided that cqrs/es is suitable for youe user/account management:...

Hi! Well you have a few options here, the one i would choose is not to implement the sequencer as an aggregate. There is one question that needs to be...

It [should be](https://github.com/GoogleCloudPlatform/google-cloud-datastore/issues/168). Might take a deeper look later on today.

Of course it can, it is a pretty common situation, they are all committed in a single commit. The revision, however, is incremented with each single event. ie. a revision...

I Really couldn't tell without at least seeing a snippet. As this behaviour is well tested ( on both eventstore and domain side ), I would guess that there is...

Your approach and solution sound interesting. Maybe writing a new db driver that either combines the whole solution ( ie redis back by mongo ) or alternatively just the redis...

Just my two cents, by looking at the driver it seems to be written for older versions of Elasticsearch ( i would say 2.x ) so even if you overcome...

@bikerp I'm not sure about the DynamoDB implementation, maybe @developmentalmadness has some insights. As of the Elasticsearch implementation, theres some work that needs to be done in order to make...

Well elasticsearch isn't exactly a database, it has some issues with error handling and it isn't recommended as a main database in any use case. When indexing new documents (...

Thank you very much! In short, iI really don't want to mess with the id logic right now. I also don't see any specific gains from this change and this...