Hard Truths About Microservices and Software Delivery [Video]
What was once one application with self-contained processes is now a complex set of independent services that connect via the network.
Join the DZone community and get the full member experience.Join For Free
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, as well as 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.
Published at DZone with permission of Anders Wallgren, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.