PASS took almost all my “free” time and I quite forgot to write a quick post to let you know that tomorrow November 8th (so I’m just right on time!) Dino Esposito – that I’m sure you all know – will deliver an interesting session for the PASS AppDev VG:

Historical CRUD and Application Business Events

Every time you update or delete a record in classic relational database you lose information. In particular, you lose the state of the entities which was current until you changed it. For many years this automatic loss of information didn’t represent a problem for companies. But now, in the days of big data and business intelligence, any data you lose is potentially money you lose. Until the release of SQL Server 2016, for updating the state of a system you had two options: lose old data or shift to another persistence paradigm like Event Sourcing. SQL Server 2016 provides an intriguing middle ground as it introduces concepts like temporal tables and native JSON serialization and indexing that combined with existing columnar indexing make it suitable to be the storage of choice even for event-driven systems. However, the real question is do you need plain Crud or domain-specific CRUD? If it’s the latter, you need to move towards Event Sourcing.

registration is free via the usual link:

http://appdev.pass.org/

and, again as usual, session will be recorded and made available on group YouTube channel couple of days after the live event.