Schedule: Anti-Pattern sessions

Moving to serverless allows you to take your application development, deployment, and economics to a new level while delivering software to your customers faster and cheaper. But there are also significant trade-offs to keep in mind. Pratik Patel takes a deep dive into serverless from an architecture point of view. 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.

Data science, machine learning, and data manipulation and preparation are all core components of a future, trendy, world of software engineering. Many of these are built with "quick hacks," tiny scripts, or based on pipelines that are cobbled together from multiple components, frameworks, and the like. Mars Geldard and Paris Buttfield-Addison explore if software architecture matters to this world. Read more.

Architectures based on microservices have spread rapidly. Organizations are drawn to the promises of microservices but fail to carry the architecture through to the frontend, resulting in the dreaded frontend monolith. Erik Dörnenburg explores patterns harvested from practical use that show how to build micro-frontends to realize the benefits of microservices in systems with rich user interfaces. 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.

The paradigm billboard reads, "Object-oriented failed." Vaughn Vernon explores the ways developers have failed at object-oriented compared to the use objects their inventor intended. Reactive domain-driven design (DDD) features explicit, coherent, message sending that employs simple, business-centric, concurrent objects. Read more.

Stefan Tilkov takes a look at some of the ways you can determine whether the development efforts you're undertaking suffer from too much or too little focus on architecture. You'll examine a number of real-world examples that are intended to inspire either admiration or terror and try to find some recipes of how you can get more of the former and less of the latter in your own projects. Read more.

Your organization has grown and now you need to break down product silos and leverage a common platform to move to the next big step. Join Sidney Shek and Diogo Lucas to hear to the ups and downs of a platformization journey, where they address the features you need to platformize and when, how much design is enough for a platform service, how to handle the mass adoption of your service, and more. Read more.

Sidney Shek and Jeff Farber explain how to use techniques like event sourcing, CQRS, and CRDTs to mitigate unpredictable failures that stem from humans and increasingly complex architectures in the cloud native world (microservices, anyone?). You'll learn implementation tips and tricks based on their successes (and failures) in building out the Identity platform that underpins Atlassian Cloud. Read more.