YOW! Night 2018 Sydney – Neal Ford – June 6

 

Stories Every Developer Should Know

Those who cannot remember the past are condemned to repeat it. –George Santayana

The past is never dead. It’s not even past. –William Faulkner

Most developers pursue the Latest and Greatest with intense fervor, yet the history of engineering, including software projects, contains rich lessons that we risk repeating ad nauseam. This session recounts a variety of stories of projects that failed…and why. Ranging from the Vasa in 1628 to Knight Capital in 2012, each story tells of a mistaken interpretation of some architectural fundamental principle and the consequences–some good, some less so. I also look at the common threads for these stories, which resonates with problems many companies have but don’t realize.

Download Slides

YOW! Night 2018 Sydney/Bne/Perth/HK/SG – Sebastian von Conrad – June 12,13,14,26,28

 

Go Back to the Future with Event Sourcing and CQRS

Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

What is Event Sourcing, and how does it differ from systems designed around current state.
Interpreting Events into denormalised projections for very fast reads (Queries).
Receiving and validating Commands that, if successful, result in new Events.
Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

See the photos here

Download Slides

YOW! Night 2018 Singapore/Hong Kong – Evan Leybourn – May 28,29

 

Certain Uncertainty

The world is changing more rapidly than ever before and organisations of every size are struggling to remain relevant in the eyes of their customers. The simple fact that the average lifespan of a company has decreased by more than 50 years in the last century demonstrates that not all organisations are prepared for this new reality. It is only high-performing, adaptable and agile organisations that will leverage, lead and thrive in this ambiguous and unpredictable market. We call this business agility.

The problem with a statement like that is that there is no common definition of what business agility means. And that’s actually a good thing. In a dynamic and changing market trying to lock it down will defeat the very advantage it brings. Instead, I want you to start thinking of business agility as the common thread. An adaptable and sustainable narrative that binds & guides, rather than directs, us into the uncertain future.

This talk will share the state of business agility around the world. We’ll look at the Domains of Business Agility, interspersed with case studies from 4 multinational organisation in both the banking and utilities sector.

Check out the presentation slides here!