You can implement an Agile process perfectly, but if you don't have an architecture that handles the stress of changing requirements, you will fail. Traditional, monolithic n-tier systems, including service-oriented architectures, just don't cut it. Allen Holub offers a two-day hands-on deep dive into designing and architecting systems that are robust in the face of change.
Fundamentals of software architecture
Mark Richards (Self-employed)
Being a software architect involves more than just drawing boxes and lines. It requires thinking like an architect, being a leader, and understanding the elements, patterns, and styles necessary to create effective software architectures. In a 2-day training course blending lecture and hands-on real-world group exercises, Mark Richards explores the many aspects of software architecture.
Transitioning to microservices: Evolutionary approaches for building systems of systems
James Lewis (ThoughtWorks)
The accepted wisdom for 40 years has been to write programs that do one thing and do it well, yet we have spent the last decade building monolithic applications and communicating via bloated middleware, hoping that Moore’s law keeps helping us out. There's a better way: microservices. James Lewis explores a consistent and reinforcing set of tools and practices for transitioning to microserves.
Reactive and its variants
Reactive system design
Duncan DeVore (Lightbend)
Are you building distributed apps? If so, you need those apps to be responsive, resilient, and elastic in the face of both failure and extreme load. Duncan DeVore explores the tenets of reactive programming before walking you through practical exercises that lead to a fully functional reactive application.
Break: Morning coffee | Room: Foyers: Monarch Suite / King's Suite ~ 10:30 - 11:00 Morning Break