Schedule: Theoretical sessions

Software engineers usually find themselves changing hard-coded content on the presentation layer, changing a paragraph here and there; that’s difficult to maintain and hard to scale. Now imagine you have to support and apply the same changes on a website and other devices. Edwin Maldonado outlines the basics so you can design a reusable information architecture. Read more.

Pini Reznik shares a story drawn from real-world migration projects that demonstrates a transformation design and reveals related patterns, including failures along the way. By the end, it establishes a full pattern language. Read more.

Ubiquitous APIs and ever-growing distributed systems brought major challenges with complexity and discovery, which can no longer be overcome by hiring more people. We need to architect our systems differently. Enter autonomous APIs. Zdenek Nemec explores the problems with the complexity of forming API landscapes and proposes the autonomy of the components as the solution. Read more.

"It's just semantics." Semantics is all about meaning. If there's one thing we struggle with and need to get better at, it's the search for and clarification of meaning. Kevlin Henney explores how the very act of software development is an exercise in meaning—its discovery, its formulation, its communication. Paradigms, processes, and practices are anchored in ways of arriving at meaning. Read more.

Software is changing the world, and software developers need to open their eyes to the link between ethics and software. Rotem Hermon outlines some examples of ethical questions involving software and algorithms. You'll explore technology, sense of self, politics, and truth, and you'll try to understand what you can do about it. Read more.

Events are our industry’s near and dear. All technological conferences are full of talks on event sourcing, event-driven architectures, or event-driven integrations. Vladik Khononov adds another one, but a bit different. Let’s talk about the dark side of this pattern—the cases in which events turn into an anti-pattern, how to identify them, and, of course, how to turn the project around. Read more.

Everyone doing large-scale software delivery is using domain-driven design (DDD) these days, because it holds the key to delivering maintainable, evolvable solutions with independent teams. But it can go wrong, and then DDD is blamed. Andrew Harmel-Law and Gayathri Thiyagarajan detail a real project they saw fail. You'll learn the many problems they spotted and how they fixed them. Read more.

Robin Moffatt explores the concepts of events, their relevance to software and data engineers, and their ability to unify architectures in a powerful way. Join in to learn why analytics, data integration, and ETL fit naturally into a streaming world. Along the way, Robin leads a hands-on demonstration of these concepts in practice and commentary on the design choices made. Read more.

Conflict-free replicated data types (CRDTs) promise strong eventual consistency for highly available systems without the costs of coordination. John Mumm explains the theory behind state-based CRDTs, which might seem intimidating at first glance, but it's actually built out of familiar elements. And it turns out that this theoretical basis can be useful for implementing CRDTs in practice. Read more.