Hi Vaughn, Thanks again for your insight. Your explanation clarifies a lot.
-Prakhyat M M On Thursday, 11 September 2014 12:18:35 UTC+5:30, Vaughn Vernon wrote: > > Events first keeps you strictly on business process, which is how the > business thinks. Typically focusing on aggregates first can drive you > toward a more technical model, and you will tend to confuse the experts > with discussions about aggregates (which they don't understand, nor should > they be forced to understand). Business people can very easily understand > events. > > This doesn't mean that you can't model aggregates first, but don't make it > a technical discussion. You will have to discuss purely on the topic of > mental model concepts. > > The other problem is that if you remain too aggregate focused your > aggregates will probably suffer from bloat and you will create large > aggregates. If you model event centric then you can choose the size of your > aggregates as a side-effect of understanding the business process and you > can probably do a better job of designing smaller aggregates that are > eventually consistent with the others. > > > On Thursday, September 11, 2014 12:17:02 AM UTC-6, Prakhyat Mallikarjun > wrote: >> >> Hi Vaughn, >> >> Thanks for insight and guidance. >> >> I always had this confusion where to begin with first events or domain. >> Your input clarifies a lot. >> >> But I have one fundamental major question, consider if we one takes up >> domain modeling first and later events, what one will loose? or any >> impacts/problems?what kinds of defects will occur? >> >> What benefits we can reap by doing events first? >> >> -Prakhyat M M >> >> On Thursday, 11 September 2014 07:59:07 UTC+5:30, Vaughn Vernon wrote: >>> >>> Hi Prakhyat, >>> >>> I have successfully involved domain experts in project-specific >>> workshops using a Model/Event Storming approach that led to model >>> development using Akka. If you have a change to attend one of my workshops >>> we go in to Event Storming as a classroom exercise. Otherwise, you might >>> search online for content by Alberto Brandolini and Model Storming. >>> Basically it involves making Events the primary language tool (event types >>> in the past tense and in time order from left to right). After several >>> cycles through refining steps (maybe a few days) you finally add Commands >>> (verbs) and Aggregate (data nouns) as a technical step to understand where >>> your actors are, but this takes a backseat to the Events which define the >>> start-to-finish business process. Depending on the complexity of your >>> business process you can probably get through the whole exercise in 2-3 >>> days. (I say this because you may think you can finish in 1 day, but >>> basically sleeping on your conclusions for 1 or 2 nights will open up new >>> modeling break-throughs.) >>> >>> In my latest effort we completely disrupted the CIO's project direction >>> with a much better and much more insightful business process, which is what >>> Model/Event Storming leads to. >>> >>> Best, >>> Vaughn >>> >>> On Monday, September 8, 2014 5:16:40 AM UTC-6, Prakhyat Mallikarjun >>> wrote: >>>> >>>> Hi Team, >>>> >>>> What is the recommended way for DDD with event sourcing? >>>> >>>> Which comes first aggregate routes modelling or events to the system? >>>> >>>> Wanted to understand will event sourcing impact designing aggregate >>>> roots of the system? >>>> >>>> What are the recommendations or knowledge required for Business experts >>>> to work with event sourcing systems? >>>> >>>> Is any expertise required by Business experts to design model in event >>>> sourcing system? >>>> >>>> -Prakhyat M M >>>> >>> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
