The Future of Containers and Microservices

DZone 's Guide to

The Future of Containers and Microservices

This interview addresses some of the questions around microservices and containers in development and looks into their possible future.

· Microservices Zone ·
Free Resource

Microservices are emerging as the preferred way to create enterprise applications, bringing a wide range of advantages such as isolated risk and faster innovation, flexibility and agility.

As more enterprises are laying the foundations for more agile and services-based architectures, we’ve asked Petrica Martinescu, Lead Architect in Tremend, for his perspective on where does the industry go from here:

Q: Where are companies when it comes to container and microservices adoption?

A: We have been working with containerized applications for some years now and we see more and more clients focusing proactively on adopting a microservice based architecture for their internal infrastructure. The key takeaways in making this adoption smooth are flexibility in choosing the right technology for the job, modularization of the application, streamlining the process of spinning up new environments and accelerating the development process by working in parallel on multiple functionalities using smaller, more agile and self-governed engineering teams.

Q: How do you see container and microservices adoption changing in large enterprises in the year ahead?

A: The change will happen gradually, slow at first and then more and more accelerated as large enterprises develop knowledge and the right processes in place to sustain a containerized infrastructure. Enterprises will make use of strangler pattern to gradually migrate their monolithic applications to microservices based ones.

Q: What impact will containers and microservices have on IT efforts to automate processes?

A: Containers are taking the IT industry by storm. If you need to run a particular open source application or library, you quickly develop the habit of searching for the dockerized version of it and that’s it. No need to install additional software or worry about specific configuration for running the application in your local environment. In a matter of minutes, you could be running your microservice based application in a completely different environment.

Q: What are some of the biggest barriers to container and microservices adoption today?

A: Though it is not a new concept to decompose an app into smaller logical units now called microservices, it also requires the availability of mature tools, processes, and best practices. Adopting microservices requires complex CI/CD (Continuous integration and Continuous deployment) processes, distributed monitoring tools, centralized logging, complex integration tests, complex configuration, a team of developers ready to take the hassle of debugging an app made of smaller components. All in all, it’s a shift of perspective.

Q: How will they be overcome?

A: In the short term, it takes a handful of talented software engineers, ready to redefine what it means to develop enterprise applications, to overcome the barriers to a container and microservices adoption. In the long run, more and more companies will adopt microservices and this will generate a need to produce more and more tools that will help simplify the overall process.

microservices ,containers ,containerization

Published at DZone with permission of Valentina Iorga . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}