Schedule List ViewGrid View

Today, your product's success depends on the creation of experiences in a steadily rising number of channels, leading to increasing demands for your content management system. Stefan Judis explains how Contentful’s content infrastructure helps developers on the frontline fetch the data they need, ship modern websites faster, and automate content distribution while using their favorite tools.

More and more enterprises are developing modern applications centered on Node.js, but with no de facto reference architectures yet for full stack JavaScript apps, many enterprises are struggling to get repeatable success. Paul Savage shares a warts-and-all dive into modern JavaScript development, covering npm, security, performance, and how projects like Node.js are being maintained.

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

The future of software is being driven by intelligent applications. By the year 2020, more than 85% of customer interactions will be carried out without humans. The road to enterprise intelligence starts with the humans behind the curtain. Kishau Rogers explains how to reduce the friction of AI adoption in the enterprise using systems thinking and people-centered workflows.

Integrating microservices and taming distributed systems is hard. Most people still integrate via REST but are not even aware of missing consistency guarantees in these architectures. Bernd Rücker shares three challenges he's observed in real-life projects and demonstrates how to avoid them, using live coding.

There are numerous standards and best practices to describe and document APIs, but there's still uncertainty how to best use them to combine API description, documentation, and labeling. Erik Wilde offers an overview of the existing approaches, demonstrates how to use them, and proposes an additional layer on top of which API labeling becomes more unified, and thus more useful.

Wenbo Zhu illustrates the key architectural properties and underlying technologies to create and deploy a real-time, stateful application on top of the completely stateless serverless architecture.

Eben Hewitt shares technology strategy patterns for creating and communicating a compelling technology strategy based on architecture principles. Some of these frameworks originate in the world of business strategy consulting and some are hard-won from Eben's time as a CTO and chief architect. Join in to upgrade your skills from architect to strategist using these proven and innovative patterns.

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.

Dan Haywood explains how he and a tiny one-and-a-bit-pizza team used Apache Isis—an implementation of the naked objects architectural pattern—to build an invoicing system, Estatio. You'll see what an Apache Isis app looks like in the flesh and learn how Dan and his team manage to keep it modular.

Chaos engineering is a discipline that focuses on improving system resilience through controlled experiments that expose the inherent chaos and failure modes in your system. While most of the publicized literature and tools focus on killing EC2 servers, Yan Cui explains how to apply the same principles of chaos to a serverless architecture built around AWS Lambda functions.

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.

Chaos engineering helps you gain trust and confidence in your system of software development and delivery, but it is often misunderstood to be only about breaking things, and worse only about breaking infrastructure. Russ Miles debunks those limitations and demonstrates how chaos engineering can be a full part of your resilience engineering capability.

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.

An Akka expert and a Kubernetes expert walk into a bar. They order drinks and try to figure out which technology is better for building distributed applications. Does Akka clustering have a place in the age of Kubernetes? Does Kubernetes bring any value to those who are building applications using Akka? Adam Sandor and Fabio Tiriticco share research to help answer those questions.

Building microservice architectures is complex. Handling the involved complexities is usually left up to the development teams to implement. Using open source components to address these challenges is an option, but this quickly leads to excessive library bloat in your microservices. So let's put them on a diet—with Istio. Join Mario-Leander Reimer to learn how.

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.

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.

Launched 10 years ago, the BBC's iPlayer on TV has become the largest iPlayer platform. David Buckhurst and Ross Wilson explore the evolution of the BBC's TV application architecture, from the early days courting different native technologies to the development of an open source library and standards-based platform that supports multiple BBC applications across thousands of TVs.

While there are differences between serverless architecture and microservices architecture, both require an application to be composed of a collection of loosely coupled components. Thus, it is possible to implement microservices architecture as a serverless application. Nikhil Barthwal elaborates, covering the pros and cons, details of various deployment patterns, and best practices.

Leemay Nassery explains the importance of data collection pipelines and walks you through efficiently storing various datasets. Join in to learn how to avoid the "pipeline jungle" construct by thinking holistically about the data and the tiers that follow the initial consumption of these events.

Drawing on her experience as a developer in IBM's Cloud Garage, Holly Cummins shares stories of customers struggling to get cloud native and explains how IBM applied its methodology to turn things around. You'll learn the ideal team size, the ideal microservice size, what skills a team needs, the role of architects, how to know if something is ready to ship, and whose fault everything is (joke).

Though you can design microservices to talk to each other synchronously, as if they were making function calls, that's not the best way to do things. Choreographed (asynchronous) systems solve many problems inherent in synchronous (orchestrated) communication. Allen Holub shows you how to build effective choreographed microservice systems.

If you want to develop high-quality products, you need happy developers and strong feedback loops. Yiannis Kanellopoulos and Evelyn van Kelle discuss the factors that determine developer happiness, explore the crucial relationship between developer happiness and code quality, and explain how to enhance overall code quality through a blend of interpersonal communication and tool-based analysis.

And you shall do it only once. Exactly once. That's a very common assumption for most of business software. One trigger equals one outcome. Szymon Pobiega explains why duplicate messages are a fact of life in distributed systems (and why no infrastructure can help you). Fortunately, Szymon also shares tips on how to deal with nasty duplicate zombie messages.

Software architects and enterprise architects work with a variety of roles, and often the deep technical work is performed by other application architects or solutions architects. Maggie Carroll shares useful skills and actionable techniques for creating a new architecture function and leading other architects in developing a system of systems.

As people with strong technical backgrounds, we know how to get most out of the tools and devices we use, but this doesn't necessarily guarantee best results on a team. Bulama Yusuf explores proven ways to communicate and connect with a team as a software architect, ensuring that your team is working at its best.

Program chairs Mary Treseler and Neal Ford welcome you to the first day of keynotes.

How do you decide whether to adopt a leading-edge technology? The Financial Times recently migrated its content platform to Kubernetes. Join Sarah Wells to find out what it takes to migrate 150+ microservices from one container stack to another without affecting the existing production users and while the rest of your teams are working on delivering new functionality.

Liz Rice explores the security implications of microservices, containers, and serverless and addresses the questions you need answers to: Will your deployments be less secure or more? How do DevOps processes like CI/CD and cluster orchestration affect your security profile? And what can we all do to minimize the risk of exploits?

Chris Richarson details several anti-patterns of microservices adoption that he's observed while working with clients around the world. You'll learn the challenges that enterprises often face and how to overcome them as well as how to avoid the potholes when escaping monolithic hell.

Closing remarks

Jumpstart your networking at Software Architecture by coming to Speed Networking before the keynotes begin. Bring your business cards and prepare a minute of patter about yourself, your projects, and your interests.

Join other attendees during lunch at Software Architecture to share ideas, talk about the issues of the day, and maybe solve a few. Not sure which topic to pick? Don’t worry—it's not a long-term commitment. Try two or three and settle on a different topic tomorrow.

Join us in the Sponsor Pavilion after the afternoon sessions to visit the exhibitors, mingle with other attendees, and enjoy great refreshments and drinks.

Looking for dinner plans Monday night? Sign up to join a group of fellow attendees for the Software Architecture Dine-Around.