Microservices design and deployment patterns have gained prominence in the TSP industry to boost business agility and operational efficiency in the light of evolving digital environments.
The term “microservices architecture” (MSA) stems from the IT applications architecture world. MSA is a composite of the various types of application infrastructure technologies used to build, deploy, run and manage fine-grained distributed application components (microservices).
Digital innovators and over-the-top (OTT) players, such as Airbnb, Dropbox and Twitter, have achieved significant development agility and time-to-market improvements of up to 75% by adopting this approach.
Tech leaders are now exploring the option adopt microservices to solve agility problems in evolving software-driven, cloud-native service delivery infrastructures. While microservices are part of cloud-native architectures, there is also an option to create cloud-native applications without using microservices.
Currently we see an inflated use of the term microservices in the industry. Vendors are frequently looking to differentiate their technology offerings, labeling them as “microservices based.” Some TSPs claim their products either use, support or create microservices. However, in some cases it means is that they provide “services” rather than “microservices.”
The anticipated benefits of MSA will only be realized by solving specific problems in a well-defined solution scope, as broad adoption may become complex and expensive. TSPs need to consider the key impacts of microservices architectures to ensure successful, targeted deployment for their organizations. This means balancing benefits with potential risks.
TSPs can generate an early mover advantage, but only if they embrace the prerequisites to achieve the actual benefit from MSA. For more details please read: Tech CEOs Must Evaluate Microservices Architecture to Establish If There Are First-Mover Advantages.
One major implication is that MSA is a post-DevOps capability. Without a continuous change in demand, and an organization that’s already prepared to develop rapidly, MSA will be at best a marketing bullet point.
That means before adopting micro patterns, TSPs need to be good at developing software using modern practices including agile, DevOps and CI/CT/CD. Furthermore it makes most sense to implement MSA in cases where organizations need the ability to develop and deploy nearly continuously. TSPs who are on a quarterly release schedule might not be able to fully take advantage of MSA.
Particularly TSPs looking to deliver MSA in a SaaS based delivery model, can take advantage the innovation potential of this new technology, by fully managing the deployment of new features. This allows TSPs to cater to evolving demands for usage-based digital business models leveraging MSA in an as-a-service fashion.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.