It seems as if the whole world of software development is jumping on the bandwagon to move to a microservices architecture. There are many good aspects to architecting a system in this fashion, but what about the downsides? Are microservices a silver bullet—will they solve all our problems?
In a knockdown debate, Rachel Laycock and Cassandra Shum take opposing sides on whether to implement services in a micro fashion and deliver zings and gotchas about the pros and cons of microservices, leaving you with a better understanding of considerations for choosing the best approach for your projects.
Cassie Shum is the technical director and principal consultant for the east portfolio in North America at ThoughtWorks. A software engineer and architect, she’s spent the last nine years focusing on architectures including event-driven systems and microservices, a wide range of technologies with an emphasis on mobile and software delivery excellence, and she’s helped grow delivery practices and technical strategy and support the next generation of technologists. Some of her passions include advocating for women in technology and public speaking. She’s involved in promoting more female speakers in technology.
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.
Comments on this page are now closed.
©2016, O'Reilly Media, Inc. • (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