It’s a shame this year’s Microsoft Developer Days does not cover anything of the work the Patterns & Practices team is doing. However I know from first hand that they’re doing a very good job. A few weeks ago, you were given the opportunity to vote for your favorite feature or improvements, and now, they’ve delivered their first drop. And while you’re reading about it, notice that P&P is actually using (a variation) of SCRUM, hence their reference to Sprints.
You May Also Enjoy
4 minute read
Het was januari 1997. Ik was net afgestudeerd van de HTS Electrotechniek. Trots als een pauw op mijn ingenieurstitel én die dikke 9 voor mijn afstudeeropdracht bij - toen nog - Philips Semiconductors, ging ik op zoek naar een job. Maar dat viel nog niet mee. Philips had een aannamestop en van rec...
September 13, 2018
4 minute read
Transient vs non-transient exceptions If I have to name the single biggest flaw in adopting Event Sourcing, it must be our decision to rely on the synchronous dispatching pipeline of NEventStore. It is based on the idea that every event will be processed by all projectors in a synchronous manner....
July 25, 2018
9 minute read
I thought we didn’t need OR/Ms anymore? A common advantage of adopting Event Sourcing is that it solves the impedance mismatch between object oriented code and the relation database model. And because of that, Object/Relational Mappers (OR/Ms) have become obsolete. While I agree with the first st...
July 15, 2018
12 minute read
The characteristics of a great projection implementation Over the course of the last two years I’ve written numerous articles on the good, the bad and the ugly of Event Sourcing as well as on our experiences building and maintaining a distributed enterprise-class based on this increasingly popula...
May 18, 2018