BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:&quot\;The fundamental idea of Event Sourcing is that of ensur
 ing every change to the state of an application is captured in an event o
 bject\, and that these event objects are themselves stored in the sequenc
 e they were applied for the same lifetime as the application state itself
 .&quot\; - Martin Fowler\n\nWhat if we could start with a very simple Dom
 ain Model and be able to see every state transition that ever took place 
 within the system AND recreate them at any time.  Doing this in classic t
 hinking is not only incredibly difficult it is usually impossible or impr
 actical.  This is a large paradigm shift that moves us away from the clas
 sic RDBMS thinking as the center of our universe.\n\nAs our Domain gets m
 ore and more complex\, communicating and understanding the relationships 
 between Domain Entities becomes overwhelming.  This Pattern is quiet ofte
 n paired with CQRS\, but is a distinct pattern of its own and has signifi
 cant aspects that need to be considered before adapting it.\n\nCome learn
  how to think in terms of Events and Aggregate Roots\, not just in your P
 resentation Layer\, but in your entire Domain Model.\n\nThis Session will
  cover several Patterns of Enterprise Architecture\, thinking in terms of
  Domain Events and how to create that in Code.
DTEND;TZID=America/Phoenix:20141018T151500
DTSTAMP:20260308T043623Z
DTSTART;TZID=America/Phoenix:20141018T141500
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-124
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:&quot\;The fundamental idea of Event Sourcing is that of ensuring 
 every change to the state of an application is captured in an event objec
 t\, and that these event objects are themselves stored in the sequence th
 ey were applied for the same lifetime as the application state itself.&qu
 ot\; - Martin Fowler\n\nWhat if we could start with a very simple Domain 
 Model and be able to see every state transition that ever took place with
 in the system AND recreate them at any time.  Doing this in classic think
 ing is not only incredibly difficult it is usually impossible or impracti
 cal.  This is a large paradigm shift that moves us away from the classic 
 RDBMS thinking as the center of our universe.\n\nAs our Domain gets more 
 and more complex\, communicating and understanding the relationships betw
 een Domain Entities becomes overwhelming.  This Pattern is quiet often pa
 ired with CQRS\, but is a distinct pattern of its own and has significant
  aspects that need to be considered before adapting it.\n\nCome learn how
  to think in terms of Events and Aggregate Roots\, not just in your Prese
 ntation Layer\, but in your entire Domain Model.\n\nThis Session will cov
 er several Patterns of Enterprise Architecture\, thinking in terms of Dom
 ain Events and how to create that in Code.
UID:1b7df5c8-807c-4244-8e79-e30096a046e0
END:VEVENT
END:VCALENDAR
