Schedule: Microservices sessions

An evolutionary architecture supports incremental, guided change across multiple dimensions. Read more.

Jim Gough shares his experience moving from a traditional monolithic architecture to a single API composed of many microservices, along with some of the challenges it presented. Jim also explores technologies and patterns with a mixture of hands-on examples and discussion topics and considers the impact to team culture and Agile practices required to achieve operational excellence. Read more.

Think of this talk as a Microservices 201. You know microservices basics, but can you successfully maintain them in production? Join Maria Gomez to explore the concept of observability as a way of maintain a healthy production environment. Read more.

Fahran Wallace explores the intersection of programming, architecture, and psychology through the medium of funny-in-retrospect memories, borrowed war stories, and attempts to avoid people swearing at her design choices five years later. Read more.

Microservices have quickly become a popular way to develop software systems. But as organizations implement production systems based on microservices, they are recognizing the importance and complexity of securing microservices. Rob Wilson shares techniques for securing microservice APIs and details a practical multiplatform model that you can use for securing your own microservice environments. Read more.

Microservices are all the rage these days. But what practical factors should you consider once you’ve taken the plunge? Marco Palladino provides a working framework of the architectural and organizational decisions senior technologists will need to make in order to solve the right problems for their business. Read more.

Dennis Bijlsma and Haiyun Xu explain how to measure the maintainability of software landscapes that consist of many systems communicating with each other—and what that means for the teams working on them. Along the way, they explore a number of trade-offs to consider when designing the landscape and share best practices for modern software landscape architectures. Read more.

Microservices is a popular but vague term. Definitions of microservices can vary depending on what you want them to accomplish and how you want them to communicate with each other. Join Mike Amundsen to learn about the three types of microservices, see what makes them unique, and discover when you deploy each of them. Read more.

With cloud-native and microservices architecture gaining wide adoption, asynchronous programming patterns are becoming increasingly important. Irakli Nadareishvili details three major async forms that are relevant in this space—event sourcing, reactiveness, and data streams—defining each pattern, explaining relevant use cases, and exploring differences in implementation. Read more.

Continuous delivery for 12-factor microservices works by design. When you can architect a solution for continuous delivery, you control all the angles. But what do you do when you don’t have that luxury? Brad Topol explains how modernizing existing IT infrastructure with containers enables you to manage change through continuous delivery and reduce ongoing operational costs. Read more.

Tobias Uldall-Espersen and Thomas Krogsgaard Holme explain how they applied microservice architecture and privacy by design principles to break down a monolithic portal containing 50+ products—the Danish national ehealth portal Sundhed.dk—redesign it, and produce a scalable and flexible platform in compliance with the EU General Data Protection Regulation (GDPR). Read more.

One of the most interesting and provocative patterns to face the software architecture community is the idea of using event streaming as a source of truth—a pattern where replayable logs provide both communication and storage, splicing the retentive properties of a database into a system designed to share data across teams. Benjamin Stopford explains why this pattern is transformative. Read more.

The architectural principle of CQRS makes great promises about the scalability of applications. Allard Buijze and Nakul Mishra elaborate on these promises and explain how to bring them into practice. Along the way, they provide insight into the challenges Casumo faced while scaling from thousands to billions of events and how they were resolved. Read more.