Agile practices and techniques like continuous delivery and evolutionary architecture are all about being able to react to changes rapidly. However, putting them into practice when you have a big legacy monolith application can be a difficult job. The industry has come out with different ideas to solve this problem; microservices, pushed by companies like Netflix and Amazon, are the latest solution.
Having an architecture based on services offers many advantages (like scalability and technical flexibility), but it comes with upfront costs and complexity that few companies are in a position to pay. Cassandra Shum and Ryan Oglesby explore the prerequisites for moving into a microservices architecture and provide tips on how to achieve them via engaging exercises.
Cassie Shum is the technical director for the east portfolio in North America at ThoughtWorks. A software engineer and architect, she’s spent that 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.
Ryan Oglesby is an application developer at ThoughtWorks, where he has worked on products ranging from native mobile applications to an enterprise banking platform built on domain-driven design, CQRS, and event sourcing. Ryan is currently a senior consultant and technical lead who builds high-quality, valuable software as well as strong technical community among teams through communication, empathy, and inclusivity.
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. • email@example.com