-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion of next meetup for May+ talk about practical Event Storming Session in a real life use case #7
Comments
There is also another topic that I find interesting, the one in this issue: |
Regarding #4 I'm still interested in doing some research into this topic and present potential findings but not until May. @virgiliolino, you are in contact with someone who could present a real life CQRS usecase? Any concrete on this? |
Hi @virgiliolino regarding point 1: From where you have this expression? In my former company we introduced EventStorming in several teams and collected learnings. For sure i can share these experiences. |
Hi @mamuz, my mistake, it was Marcelo who suggested that topic. But of course the more experience we can share the best it will be. |
Hi @Partyschaum, yes I'm in contact with him. Its a real life project they are building, not much DDD, but yes, it's still a CQRS project. Currently they are in the process of discussing ES, but lets keep it on what they actually build. |
Looks like a nice suggestion. What do you guys think about those two talks for may:
If you're agree please give me an ok. @Partyschaum what do you think? |
Hi, somehow I overlooked that you are putting together the May meetup. I will be on vacation for most of May. But I would be happy to contribute in June or later. |
So, if noone is agains it I would comeback to:
Please think and let me know |
Marcelo that was there on the last meetup contacted us suggesting a new meeting for the mid of May
and talk about their practical experience they had with Event Storming.
Possible talks:
I'd like to suggest the beginning of May.
Please give your comments
The text was updated successfully, but these errors were encountered: