It seems as if the whole world of software development is jumping on the bandwagon to move to a microservices architecture. There are a lot of good aspects to architecting a system in this fashion, but what about the downsides? Are microservices a silver bullet and will they solve all our problems?
Rachel and Cassie will present a debate in which they take opposing sides on whether to implement services in a “micro” fashion. In a knockdown style, our discussion will feature the zings and gotchas to each side of the argument. The debate will ultimately leave attendees with a better understanding of the things to consider and practices to follow to decide whether or not microservices are the best approach for them.
Rachel Laycock is a market technical principal at ThoughtWorks in New York, where she has played the role of coach, trainer, technical lead, architect, and developer, coaching teams on Agile and continuous delivery technical practices. She is now a member of the Technical Advisory Board to the CTO, which regularly produces the ThoughtWorks Technology Radar. Rachel has over 10 years of experience in systems development and has worked on a wide range of technologies and the integration of many disparate systems. She is fascinated by problem solving and has discovered that people problems are often more difficult to solve than software ones.
Cassandra Shum is a lead consultant with ThoughtWorks, where she primarily leads and works on a variety of mobile projects and technologies, including domain-driven design and microservices. Over the last six years, she has worked on many different web and mobile applications. Cassandra is one of the leaders in the initiative to organize the women’s group in ThoughtWorks and is involved in promoting more female speakers in technology.
Comments on this page are now closed.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org