Schedule

CNN recently rated software architect the number one job in America. Yet no clear path exists for moving from developer to architect. Mark Richards blends lecture and hands-on real-world group exercises to explore the many aspects of software architecture. You'll learn various integration styles (and when to use them) as well as patterns to fit various business needs and requirements.

Join Allen Holub for a hands-on exploration of how to architect systems that easily evolve incrementally over time as requirements emerge. You'll solve a real-world problem under Allen's guidance, learning everything you need to know to go from an idea to an evolutionary implementation architecture.

As the digital economy changes the rules for enterprises, the role of architects also changes. You must connect the penthouse, where the business strategy is set, with the engine room, where the enabling technologies are implemented. Gregor Hohpe explains why making this connection by going from floor to floor won’t work. Architects bypass existing structures by taking the architect elevator.

Neal Ford and Zhamak Dehghani highlight solutions and trade-offs to architecture's difficult problems. They explore tools and practices to help you choose proper granularity of components and services, messaging styles in microservices (choreography, orchestration, sagas), and data topics, including microservices caching and data meshes, styles of reuse, and reactive architectures.

Sam Newman details framings for microservice architectures that explore the various forces that can drive the design and evolution of microservices, and he leads you through a series of interactive architectural kata exercises to put your newfound knowledge to the test. You'll gain valuable experience with a series of tools you can immediately put into practice in your own projects.

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.

Paris Buttfield-Addison, Mars Geldard, and Tim Nugent explore game design without coding or game engines. You’ll get a fresh perspective on architecture, design, and community engagement by understanding how people interact with the fastest-growing form of entertainment in the world: games. A software architect can learn a lot from game design; here you'll learn everything you need to get started.

Creating multiple models for the same problem is one of the more important lessons that domain-driven design teaches you. It's a lot cheaper to quickly iterate over them and throw away less-useful prototypes before you even start coding. Kenny Baas-Schwegler and João RosaIn explore how event storming can support modeling software with domain-driven design model-driven building blocks.

When you want to apply domain-driven design (DDD), you must first master the domain. In this hands-on examination, Stefan Hofer, and Dorota Kochanowska show you how to build up domain knowledge with domain storytelling. Domain stories help you better understand a domain, identify what is core, segregate bounded contexts, and constitute ubiquitous language.

Knowing where to start with an API program is difficult. Most development teams have been building APIs for years, but it's different when the goal is to become an API-centric team or company. James Gough, Nick Ebbitt, and Matthew Auburn bootstrap the basics from building your first API, using OpenAPI specification to describe and version your APIs, and deploying behind a gateway.

Jochem Schulenklopper and Gero Vermaas explain and practice an approach that enables you to improve and release serverless functions to production with confidence. You'll make changes in some sample serverless functions running in production, deploy the improved functions to production, and analyze your improvement against the originals.

Software architects have to practice being software architects. Now's your chance. Network and show your skills by joining Architectural Katas—a team exercise where small groups work together on a project that needs development.

Join a group of fellow attendees for dinner at the Software Architecture Dine-Around. This event is not sponsored, so you're responsible for paying your portion of the bill.