For many years, software architecture was described as the “parts that are hard to change later”. But software architecture is the balancing of capabilities versus constraints. If build changeability one of your prime capabilites, evolutionary change becomes easier. The microservice architectural style is quite popular, but it is only one in a family of evolutionary architectures. This session defines the characteristics this family of architectural styles, along with engineering and DevOps practices necessary for implementation. I cover the principles behind evolutionary architectures, the practices needed for success, how organization and team structure affects these architectures, and specific engineer practices that facilitate evolutionary architectures. I also discuss migration strategies from common existing architectural types towards move evolutionary architectures.
Neal is Director, Software Architect, and Meme Wrangler
at ThoughtWorks, a software company and a community of
passionate, purpose-led individuals, who thinks disruptively to
deliver technology to address the toughest challenges, all while
seeking to revolutionize the IT industry and create positive social
change. He is an internationally recognized expert on software
development and delivery, especially in the intersection of agile
engineering techniques and software architecture. Neal has authored
magazine articles, seven books (and counting), dozens of video
presentations, and spoken at hundreds of developers conferences
worldwide. His topics include software architecture, continuous
delivery, functional programming, cutting edge software innovations, and includes a business-focused book and video on improving technical presentations. Check out his web site at nealford.com.