The popularity of implementing microservices in today’s application landscape continues to rise, and there have been countless success stories focused on migrating from monoliths to microservices. But as more teams move toward microservices architectures, an increasing number of stories have arisen about the pain of poor choices. Microservices are not the answer to all application problems. Attempts to move away from one giant application to smaller focused services often result in a tightly coupled nest of applications.
Blithe Rocher covers some of the pitfalls and lessons learned from building several service-oriented systems. Blithe explores some of the problems with building, testing, and deploying a functional microservice architecture, from data loss to dependency nightmares, drawing on war stories she has collected and from her own personal experience. You’ll come away with some valuable lessons about microservices without having to go through the pain of experiencing them yourself.
Key questions include:
Blithe Rocher is a software engineer based in Oakland, CA. Blithe works for Fastly as part of the core engineering team to build the customer-facing Configuration API. Prior to becoming a developer, she received a PhD in physical chemistry from the University of Southern California. Blithe is passionate about teaching other women how to become developers. She helped organize Rails Girls ATL, a monthly meetup for women interested in learning about programming. When she’s not crafting web applications, she spends time traveling, riding her bike, or with her dog, Nola.
©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