Gartner Blog Network


More Than a Buzzword — Microservices-Driven OSS/BSS Architectures

by Martina Kurth  |  April 13, 2018  |  Submit a Comment

Operations support system (OSS) and business support system (BSS) architectures based on microservices will change how CSP technology leaders expedite incremental, evolutionary investments in cloud-native and DevOps-enabled microservices design and deployments, to participate in digital value chains.

The term “microservices” stems from the IT application architecture world. The microservice architecture allows for more effective customization, programmability and upgrades. Digital innovators in other industries, such as Airbnb, Dropbox and Twitter, have achieved significant development agility and time-to-market improvements of up to 75% by adopting this approach. Telcos are now looking to embrace the concept of microservices as a new architectural framework to achieve business agility, scalabiltiy and flexibility to operationalize manifold digital business models.

CSPs are typically not among the companies to first adopt cloud or cloud-only approaches as a path to effectively leverage microservices-driven OSS/BSS. Microservices imply a new way of designing and deploying Telcos services, in tandem with collaborative development and operational systems processes, to drive service agility and mitigate existing infrastructure investments.

CSPs´ approach is incremental, evolving from a complex, heterogeneous legacy environment. This situation automatically places CSPs in a detrimental position (compared to the likes of Amazon and Google). To catch up CSPs´ need to consider following actions:

• Investments in tools, people, processes and platforms that help operationalize the hybrid physical and virtual infrastructure environments
• Adoption of a platform as a service (PaaS) layer (or open source components), orchestration, as well as data repository, service modelling,      AI and DevOps tools to leverage hybrid legacy and cloud OSS/BSS environments.
• Expedite microservice architectures, driven by strong governance and underpinned by collaborative, holistic DevOps design processes   (based on continuous integration [CI]/continuous testing [CT]/continuous delivery [CD] best practices).
• Organizational, automated and agile DevOps process practices must already be in place prior to deploying microservices.
• Evolve your data management strategy to accommodate distributed data and OSS/BSS-driven microservices (leveraging OSS/BSS   artifacts).

Few early mover CSPs are at an exploratory stage regarding microservice design and deployment. Read the following Research Note on initial approaches for microservices in Telco and the impact on OSS/BSS:

Market Trends: More Than a Buzzword — Microservices-Driven OSS/BSS Architectures

Presently, the market for microservices in telco is a market instigator. Telco vendors claim that their solution architecture is truly microservices acquiescent. However, only very few new entrants offer integrated microservice architectural functionality as an independent construct, compared to that of the over-the-top (OTT) players.

Category: cloud  digital-it  

Martina Kurth
Research Director
9 years at Gartner
19 years IT Industry

Martina Kurth is a Research Director within CSP Technology advising CSPs, CTOs and CIOs worldwide on prevailing transformation and sourcing initiatives in the area of OSS/BSS and SDP. Her research also encompasses telco-specific CPQ, catalog, and order management systems and processes spanning CSPs' entire operational lead-to-install process. Read Full Bio




Leave a Reply

Your email address will not be published. Required fields are marked *

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.