Patterns and Processes for Continuous Delivery of Microservices

With just two weeks to go until Continuous Lifecycle London, I’m looking forward to joining my peers to discuss DevOps, Containerization, Microservices, and all things Continuous Delivery. The conference, which offers three days of panels, keynotes and workshops, brings together hundreds of industry experts to draw attention to the challenges of, and best practices for, modern software delivery. I’m excited to share my thoughts on the increasingly popular Microservices architectures at the show.

In the past several years, Microservices have gained attention for their ability to facilitate innovation among dev teams. By architecting applications into sets of smaller services that are more focused, dev teams can more readily make changes without having to release (and build, and test, and deploy) the entire monolithic application with each update. By splitting the monolithic application into smaller services and decoupling interdependencies (between apps, dev teams, technologies, environments and tooling), microservices allow for more flexibility and agility as you scale your organization’s productivity.

At this year’s show, I’m honored to present my thoughts on Microservices and how organizations can leverage this architecture to increase the speed and proficiency of software development. My talk will give an overview of modern requirements for creating, deploying and managing multiple Microservices both independently and as a collection in order to satisfy end user requirements and allow for Continuous Delivery. (For more information on my thoughts on the subject, you can read my interview with The Enterpriser’s Project here.)

Join me on May 3 as I discuss patterns and processes for Continuous Delivery of Microservices. Hope to see you there!