Polygot Architecture for Rapid Release: Friend or Foe?

Legends Ballroom - Robinson-Whitman

Many of us are bought into the idea of rapidly releasing through methodologies like Continuous Delivery. We now want to release when we want as often as we want, but does polyglot programming and architecture support this? Or is choosing the right development language and tool for the job at odds with rapidly releasing your software? For example, if you bring in a language is it suitable to the environment you will release to or will you cause your operations team to cry themselves to sleep at night? Or conversely can the development language and tool choices make build and deploy easier, faster and more maintainable? These are some of the questions I will address in this session. How do we choose the right architecture for our release schedule? What can we mix up at will depending on the problem space and what language and tool choices that you make in the development cycle could cause conflict with operations? We will delve into where language and tool choices are orthogonal and even make operations peoples lives a little easier and demonstrate what a build and deployment pipeline could look like in this context

Rachel Laycock's picture
Rachel Laycock works for ThoughtWorks as a Lead Consultant with 10 years of experience in systems development. She has worked on a wide range of technologies and the integration of many disparate systems. Since working at ThoughtWorks, Rachel has coached teams on Agile and Continuous Delivery technical practices and has played the role of coach, trainer, technical lead, architect, and developer. She is now a member of the Technical Advisory Board to the CTO, which regularly produces the ThoughtWorks Technology Radar. Rachel is fascinated by problem solving and has discovered that people problems are often more difficult to solve than software ones.