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, so recently the industry has come out with different ideas to solve this problem. Microservices, pushed by companies like Netflix or Amazon, are the latest solution to this problem.
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. María Gómez and Cassandra Shum explore the prerequisites for moving into a microservices architecture and provide tips on how to achieve them via engaging exercises.
Maria Gomez is the head of technology at ThoughtWorks Spain. Over her 10 years of industry experience, Maria has worked with many different technologies and domains, which has helped her lead teams and advise stakeholders in making the right technology decisions. She is also a speaker and an advocate for diversity and inclusion in the IT industry.
Based in New York, Cassie is the Technical Director for the East Portfolio in North America. As a software engineer and architect, she has spent that last 9+ years at ThoughtWorks focusing on architectures including event driven systems and microservices, a wide range of technologies with an emphasis on mobile and software delivery excellence.
Cassie has also been involved in growing not only organizations in the delivery practices and technical strategy, but also the next generation of technologists. Some of her passions include advocating for women in technology and public speaking. She is also involved in promoting more female speakers in technology.
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. • email@example.com