case study digital core: building the digital foundation ...€¦ · microservices and container:...

© 2019 TM Forum | 1#TMFDigital

GM IT Solution Architecture

Telkomsel - Indonesia

Muhammad Rayhan

CASE STUDY

Digital Core: Building the digital

foundation using microservices and

container technology


Microservices, containers, cloud-native?


B2C Customers

169M

Internet records

daily

12B

Internal Employees

5443

Telk

om

sel

in N

um

bers

Mission

Deliver mobile digital services & solutions that exceed customer’s

expectations, create value for our stakeholders, and support the

economic development of the nation.

Transformation

becoming DiCo

(Digital Telco)

Company

Telkomsel is the largest communication service provider in

Indonesia

B2B Customers

1000+Payload data

processed / day

20PB

Edge API Call

daily

200M


Back in 2014, Digital Transformation was inevitable as legacy

revenue continuously degraded

Introduce

MyTelkomsel apps


While undergoing Digital Transformation, there were change of

behavior and expectation

▪ Customer Experience

▪ Scalable Business

▪ Innovation

Introduce

MyTelkomsel apps


Digital Core decouples frontend layer against legacy BSS/OSS

stack to introduce more agility and flexibility

Digital Core

Legacy

Channel

OCS

Mobile AppsCustomer

Touchpoint3rd party

CRM PCRFService

Provisioning

Network

End-to-end product and

service order management

journey

API Management Product Catalog

Runtime pricing

Eligibility engine

Order Management

Order Fulfilment

Subscription DataSegmentation

Partner Onboarding


In 2017, we initiated Digital Core to build IT foundation to support

company-wide Digital Transformation

Digital Core

Initiated

How should we build

Digital Core? What are

the key IT principles?

Introduce

MyTelkomsel apps

© 2019 TM Forum | 8© 2019 TM Forum | 8#TMFDigital

ADAPTIVESupports agile and iterative development and delivery,

and accommodate continuous feedback and change



VELOCITYDelivers IT solution in

faster and in automated

way



SIMPLIFICATIONEliminate system complexity, coupling and duplication



QUALITYDigital customers expects operational excellence

(reliability, availability and scalability) on using CSP

services



What IT should do: from Strategic Goals to Directions

Customer ExperienceFocus on delivering the best

customer experience,

solving their problem and

adapt to their feedbacks

Scalable BusinessMore customers and

transactions, and encourage

self-service access channel

InnovationSimplify new product and

service development,

integration and

collaboration with the

ecosystem

AdaptiveSupports agile and iterative

development and delivery,

and accommodate

continuous feedback and

change

VelocityDelivers IT solution in faster

and in automated way

SimplificationEliminate system

complexity, coupling and

duplication

QualityDigital customers expects

operational excellence on

using CSP services

Microservices

Containerization

Strategic Focus IT Architectural Principles Design & Delivery Direction


Microservices

▪ Scope: small enough and

focused on doing one thing

well

▪ Organized around business

capabilities

▪ Autonomous

▪ Flexibility to use the best

technology


HOW TO DO SERVICE DECOMPOSITION?


Photo by Sharon McCutcheon from Pexels

https://www.pexels.com/@mccutcheon?utm_content=attributionCopyText&utm_medium=referral&utm_source=pexels

https://www.pexels.com/photo/art-materials-art-supplies-blocks-blur-1148496/?utm_content=attributionCopyText&utm_medium=referral&utm_source=pexels


Microservices Decomposition Use-case: Order Management

▪ Tightly-coupled

▪ Redundancy / duplication

▪ Rigid yet error-prone to

change

▪ Difficult to scale

USSDMobile Apps

Traditional Prepaid

Order Management

Taxonomy

Commercial

Catalog

Subscription

Data

Rule

ValidationFulfilment

Modern Prepaid

Order Management

API

Management

Subscription

Data

Technical

Catalog

Rule

Validation

Commercial

Catalog

API

Management

Technical

Catalog

Fulfilment

Taxonomy

Online

ChargingPCRF

Network

ProvisioningCRM

Customer

Segmentation

Customer

Segmentation


Product Catalog


USSDMobile Apps

Traditional Prepaid

Order Management

Taxonomy

Commercial

Catalog

Subscription

Data

Rule


Modern Prepaid

Order Management

API

Management

Subscription

Data

Technical

Catalog

Rule

Validation

Commercial

Catalog

API

Management

Technical

Catalog

Fulfillment

Taxonomy

Online

ChargingPCRF

Network

ProvisioningCRM

API Gateway & Management

Order Fulfilment

Technical Catalog

Commercial

CatalogTaxonomy

Customer

Segmentation

Pricing &

Eligbility

Engine

Customer

Segmentation

Subscriber Data

Customer

Segmentation

Online

ChargingPCRF

Network

ProvisioningCRM

USSD Mobile AppsMore

Channels


Product Catalog


USSDMobile Apps

Traditional Prepaid

Order Management

Taxonomy

Commercial

Catalog

Subscription

Data

Rule


Modern Prepaid

Order Management

API

Management

Subscription

Data

Technical

Catalog

Rule

Validation

Commercial

Catalog

API

Management

Technical

Catalog

Fulfillment

Taxonomy

Online

ChargingPCRF

Network

ProvisioningCRM

API Gateway & Management

Order Fulfilment

Technical Catalog

Commercial

CatalogTaxonomy

Customer

Segmentation

Pricing &

Eligbility

Engine

Customer

Segmentation

Subscriber Data

Customer

Segmentation

Online

ChargingPCRF

Network

ProvisioningCRM

USSDKey Benefits:

Better Agility and Organization Alignment

Single code-base, maintained independently.

Composability

Reduce duplicates & redundancy. Promote reusability and

clear segregation (single responsibility)

Scale independently

Every microservice different on different cluster. Any

service requires additional capacity can scale

independently

Technology Agnostic

Every microservice can be built using different technology

stack

Resilience

Service boundary of Microservice acts as bulkhead

Mobile AppsMore

Channels


“Architecture is abstract until operationalized”

- Neal Ford -

Operating Microservices at scale?



Things to consider for operating Microservices at scale

Deployment

Monitoring and Tracing

Failure handling

Security

Testing

Versioning


Things to consider for operating Microservices at scale

➢DevOps Culture

➢CI/CD

➢Containerization

Deployment

Monitoring and Tracing

Failure handling

Security

Testing

Versioning


CONTAINERIZATION



What are container and container orchestration platform

and why are they matter

Container▪ Software deployment unit,

packaging code and dependencies

▪ Help developers managing

dependencies easier

▪ Infrastructure abstraction

▪ Consistent environment

(development, testing, staging and

production)

▪ Automation-ready

Container Orchestrator▪ Platform to manage lifecycle of

containers

▪ Load-balancing

▪ Simplify deployment and

replications

▪ Auto-scaling

▪ Self-healing

▪ Efficiency

Container A

Container Engine

Libs

Container B

App B

Libs

Container C

App C

Libs

Host OS

Infrastructure

App A

Container Orchestrator


Containerization is not just simply put your apps on a container


Cloud-native Design Patterns

▪ https://docs.microsoft.com/en-us/azure/architecture/patterns/

▪ https://www.redhat.com/en/resources/cloud-native-container-design-whitepaper

▪ https://12factor.net/

Set of principles and design patterns for building cloud-native software▪ Large-scale container platform

deployment▪ Portability: simplify migration to

cloud infrastructure▪ Simplify automation build and

deployment

https://docs.microsoft.com/en-us/azure/architecture/patterns/

https://www.redhat.com/en/resources/cloud-native-container-design-whitepaper

https://12factor.net/


Microservices and Container: Telkomsel use-case lesson learned

▪ Ensure the team understand the principles, rationale and

best practice on implementing Microservices and Container

▪ Distributed monitoring and tracing are challenging

▪ Telemetry / Metrics

▪ Logging

▪ Audit

▪ Optimize payload: Microservices communicates using API

heavily

▪ Prepare Microservices and API security at the beginning

▪ Choose wisely: Container orchestration platform; open

source vs commercial / enterprise vs manage service

▪ Use deployment patterns to rollout your new service safely.

E.g. canary release, blue-green deployment


Digital Core: several key benefits already being realized, and now

we are ready for more challenge and exciting times ahead

Product Launched within Minutes Omni-channel Experience

High PerformanceDesigned for 30K tps

Catalog-driven Modelling and Integration

Leveraging cloud-native and containerization

Elastic and Cloud-ready Infrastructure

Agile Solution Delivery

Microservices Application Architecture Reusable API and Services


Recap: How Microservices and Container Technology support

Digital Transformation

Customer ExperienceFocus on delivering the best

customer experience,

solving their problem and

adapt to their feedbacks

Scalable BusinessMore customers and

transactions, and encourage

self-service access channel

InnovationSimplify new product and

service development,

integration and

collaboration with the

ecosystem

Strategic Focus

AdaptiveSupports agile and iterative

development and delivery,

and accommodate

continuous feedback and

change

VelocityDelivers IT solution in faster

and in automated way

SimplificationEliminate system

complexity, coupling and

duplication

QualityDigital customers expects

operational excellence on

using CSP services

IT Architectural Principles

MicroservicesAn evolutionary architecture

model to develop modern

application:

- Small and focused on

doing one thing well

- Organized around

Business Capabilities

- Autonomous

- Applying CI/CD to reduce

complexity

ContainersBest-fit deployment model

for Microservices, with the

following objectives:

- Infrastructure

abstraction & efficiency

- Enabling scaling (both

infra and team)

- Automation-ready

Design & Delivery Direction


Thank you for all partners supporting our Digital Transformation!



Thank you

case study digital core: building the digital foundation ...€¦ · microservices and container:...

Documents