Microservices Are Changing Application Development Right Now
Increased microservices adoption is being driven by mesh networks like Istio. Read on for more insights.
Join the DZone community and get the full member experience.Join For Free
To understand the current and future state of microservices, we spoke to 25 IT executives from 21 organizations. Consistent with the early adoption of the technology, the answers to our questions were diverse. We asked respondents, "How have microservices changed application development in the past year?" Here's what they told us:
- We are seeing an accelerating rate of adoption. Tools, systems, and platforms making it easier and reducing the downside making it more consumable. A spectrum of architectures – some apps don’t need to change frequently, others do, especially if they are brand new. Issues in the middle of the organization has held a couple of applications held back. The business unit wants more features and enhancements. This is the biggest opportunity for the refactoring process. Take pent-up demand and use cases to pull out portions of the larger monolith and piece together in more manageable chunks. We see a lot of decomposition happening in the middle.
- There have been changes in the ecosystem. Standards are emerging that make building microservices easier with fewer choices. K8s, OpenTracing observability, and security at different layers. Things are becoming more mature. Able to develop with fewer decisions. A lot of the tax of developing and monitoring are being taken off the table, so developers can focus more on developing the software.
- In the last 18 months, we've seen a significant shift with a lot of organizations against moving to PaaS and cloud are becoming more comfortable as they break services into microservices in the cloud. We're seeing a lot of adoption in financial and technical organizations. Security is one reason why. Large monolithic apps required big cores. Now with smaller pieces, we see a gradual shift to small sets of components into off-prem environments to meet the demands of their customers.
- The rapid adoption of mesh network management (Istio) might help the contract management portion of it – how interfaces are defined and managed. Building, managing, deploying for microservices simplification has to be clean and well-articulated. Deliver decoupling out of the box. We plug into everything standard out of the box.
- There has been more adoption such that now microservices are mainstream. It was on the fringe in 2013, now they are comfortable letting IT architects introduce microservices into IT environment. Frameworks like Kubernetes (K8s) have matured to help you run. Pivotal Cloud Foundry helps you run and focus on the business. Transition to microservices-oriented networking Istio from Google shifted thinking about sockets to microservices. Easily securable.
- We see a dramatic shift that microservices have brought with them. Ask for full-stack engineers – microservices, containers, integration scripts, CI/CD. Want engineers with the skill to do it. We've done away with classic QA. We expect developers to do QA. Developers can test microservices independently and test for security before they push code to merge. You have the opportunity to run a lot of different tests before merging into the main branch.
Here’s who we spoke to:
- Heikki Nousiainen, CTO, Aiven.io
- Chase Aucoin, Technical Evangelist, AppDynamics
- Assaf Mizrachi, Head of Software and Amit Ziv-Kenet, Backend Developer, Augury
- Bernd Ruecker, Co-founder and Developer Advocate, Camunda
- Jaime Ryan, Senior Director, Product Management and Strategy, CA Technologies
- Brian Dawson, DevOps Evangelist and Viktor Farcic, Senior Consultant, CloudBees
- Chip Childers, CTO, Cloud Foundry
- Gwen Shapira, Chief Data Architect, Confluent
- Matthew Baier, COO, Contentstack
- Anders Wallgren, CTO, Electric Cloud
- Priyanka Sharma, Director of Alliances and Andrew Newdigate, Infrastructure Architect, GitLab
- Ben Sigelman, CEO, LightStep
- Jim Scott, Director, Enterprise Strategy & Architecture, MapR
- Ariff Kassam, Vice President, Products, NuoDB
- Jim Walker, VP of Product Marketing, OverOps
- Bich Le, Chief Architect, Platform9
- Mike LaFleur, Global Head of Solution Architecture, Provenir
- Christian Posta, Chief Architect, Cloud Application Development, Red Hat
- Setu Kulkarni, V.P. Strategy and Business Development, Whitehat Security
- Asanka Abeysinghe, V.P. of Architecture – CTO Office and Kasun Indrasiri, Director, Integration Architecture, WSO2
- Roman Shaposhnik, Co-founder, Zededa
Opinions expressed by DZone contributors are their own.