Presented by Andrew Harcourt
Fred, Wilma, Betty and Barney are the best of friends. But things take a turn for the worse when they take a weekend holiday together. Fred and Barney (of course) are tasked with making the bookings, which means (of course) that Wilma and Betty have to do it at the last minute after the two boys forget.
Little did the girls know, however, that the boys were only lazy, not forgetful, and thus all four of them made their travel bookings in a mad, last-minute panic. Luckily there were still some flights and rooms available. With everything booked, confirmed and pre-paid, what could possibly go wrong?
Join us on Tuesday night for a tall tale of four friends and a hilarious, disastrous weekend away.
So… to the serious bit. We’ve all heard the term “event sourcing” but what does it mean for application design? When should we use it? When shouldn’t we? Why? And what are some of the pitfalls to be avoided?
In this talk we’ll take a first-principles look at event sourcing. There will be bad jokes. There will be code. There will *not* be PowerPoint. We’ll end up with running code that models a simple reservation/booking domain and then we’ll drop it into a performance test harness and see what consumer-grade hardware can really do.
Andrew is a solutions architect and software engineer with extensive experience in large-scale, high-load, geographically-distributed systems. Andrew specialises in project rescue, governance and development methodologies. Andrew’s main areas of interest are domain-driven design, event sourcing, massively-scalable service architectures and elastic (cloud) computing. Andrew is a regular speaker and presenter at conferences and training events. Andrew’s mother wrote COBOL on punch cards, and Andrew has been coding in one form or another since he was five years old.