Everybody’s talking about Microservices right now. But are you having trouble figuring out what it means for you?
With Microservices, what was once one application, with self-contained processes, is now a complex set of independent services that connect via the network. Each microservice is developed and deployed independently, often using different languages, technology stacks, and tools.
While Microservices support agility—particularly on the development side—they come with many technical challenges that greatly impact your software delivery pipelines, as well as other operations downstream.
During our session, Avan and I discussed some use cases that lend themselves well for microservices, and the implications of microservices on the architecture and design of your application, infrastructure, delivery pipeline, and operations. We discussed increased pipeline variations, complexities in integration, testing and monitoring, governance, and more. We also shared best practices on how to avoid these challenges when implementing microservices and designing your pipelines to support microservices-driven applications.
Watch the recording of our talk:
Latest posts by Anders Wallgren (see all)
- Continuous Discussions (#c9d9) Podcast, Episode 64: Docker & Microservices at Scale - March 14, 2017
- 4 Rules for Microservices and Software Delivery - March 1, 2017
- Continuous Discussions (#c9d9) Podcast, Episode 63: Value Stream Mapping and DevOps - February 28, 2017