Becoming the Uncarrier: T-Mobile's Digital Journey

20
©2016 Apigee Corp. All Rights Reserved. Becoming the Un-carrier: T-Mobile’s Digital Journey Himanshu Kumar, T-Mobile Paul Williams, Apigee

Transcript of Becoming the Uncarrier: T-Mobile's Digital Journey

Page 1: Becoming the Uncarrier: T-Mobile's Digital Journey

©2016 Apigee Corp. All Rights Reserved.

Becoming the Un-carrier: T-Mobile’s Digital JourneyHimanshu Kumar, T-MobilePaul Williams, Apigee

Page 2: Becoming the Uncarrier: T-Mobile's Digital Journey

T-Mobile Confidential

ENTERPRISE IT

T-Mobile’s Digital JourneyOctober 27, 2016

Page 3: Becoming the Uncarrier: T-Mobile's Digital Journey

WELCOME

Page 4: Becoming the Uncarrier: T-Mobile's Digital Journey

4 T-Mobile Confidential

4ENTERPRISE IT

Who We Are Becoming Un-carrier Un-carrier on the Inside and Digital

Transformation Digital Transformation & API First at T-

Mobile Sharing Our API Wisdom Q&A

Webinar Topics Breakdown

Page 5: Becoming the Uncarrier: T-Mobile's Digital Journey

5 T-Mobile Confidential

5ENTERPRISE ITT-Mobile – the Un-carrier

As America's Un-carrier, T-Mobile US, Inc. (NASDAQ: TMUS) is redefining the way consumers and businesses buy wireless services through leading product and service innovation. The Company's advanced nationwide 4G LTE network delivers outstanding wireless experiences to more than 69.4 million customers who are unwilling to compromise on quality and value. Based in Bellevue, Washington, T-Mobile US provides services through its subsidiaries and operates its flagship brands, T-Mobile and MetroPCS.

Page 6: Becoming the Uncarrier: T-Mobile's Digital Journey

6

Page 7: Becoming the Uncarrier: T-Mobile's Digital Journey

Un-carrier on the Inside Frequency and speed of delivery of new

capabilities becomes critical for our continued success.

Unprecedented external integration and monetization opportunities.

API economy envisioned.

Self service APIs for internal and external

consumers. Digital transformation has begun!

Page 8: Becoming the Uncarrier: T-Mobile's Digital Journey

T-Mobile Confidential

ENTERPRISE IT

Digital Transformation EnablersPeopleProcessTechnologyAchieving API First at T-Mobile!

Page 9: Becoming the Uncarrier: T-Mobile's Digital Journey

PEOPLE

PROCESS

WORLD-CLASSDIGITAL COMPANY

TECHNOLOGY

Page 10: Becoming the Uncarrier: T-Mobile's Digital Journey

: WHY APIGEE?

How it fits in overall TECHNOLOGY STACK

API management + any quick win enablers (U11.0 solution enabled using this platform)

Compliments our Microservices platform choice PCF and enables existing services on ESB out front, for consumption

Ubiquitous API exposure for API endpoints

API Management

Ease of use for developer – Edge UI, Documentation, Community Lightweight and capability to achieve speed to market Ready to use with SaaS and on-Prem + built in caching CI/CD and other tooling aligned with platform APIs Helps us achieve self serve API dev platform including ease of API consumption.

Page 11: Becoming the Uncarrier: T-Mobile's Digital Journey

T-Mobile Confidential

ENTERPRISE IT

T-Mobile ExperienceTechnology LandscapeScope & Guiding documentsWinning hearts and minds Wins & LossesImparting wisdom

Page 12: Becoming the Uncarrier: T-Mobile's Digital Journey

12

API LifecycleDesign Build Documentation Operate / Run

Internal Develop

ers

3rd Party Develop

ers

Partner Develop

ersAPI Designers API Developers API

OperatorsLeadersh

ip

Experience API

Capability API

APIGEE EDGE

Swagger

API Proxy

Policies

Resources

API Specs

json

Community

Registration

Documentation

Analysis

APIGEE PortalSecurity

RepresentationCaching

Retrieval /Aggregation

APIGEE Gateway

SecurityRepresentationCaching

PCF Spring Boot

Restful APIs

Capability

Docs Catalog Dashboards

Monitoring

Web / Mobile

UI

External Web /

Mobile UI

Experience API

Capability API Proxy

Capability API

Page 13: Becoming the Uncarrier: T-Mobile's Digital Journey

13

API Policies & Scope – Our Wisdom Security (authentication and authorization) Threat Protection – JSON, XML, SQL Injection SLA enforcement Routing Simple data and protocol transformations Payload validations Consistent error handling

Page 14: Becoming the Uncarrier: T-Mobile's Digital Journey

14

Digital LayersBrowser / DevicePresentation

Server / DeviceExperience Apps

API Gateway / Aggregation

Experience API

Cloud Native REST APIs

Capability API

Cloud Native Microservices

& Data

Capability App/Service

s

Event BusEvents SOA Services

Internal / External

DC/Hybrid Cloud

ESB SOA Services

Capability Applications /

Platforms DC/Hybrid Cloud

System Of Record

Expe

rienc

eCa

pabi

lity

Landing Page

UI App1

/v1/landing/app1/summary

capid/v1/entity2/{id}

capidx/v1/entity3/{id}/subs

Capability1 entity2

Capability2entity3

Entity-accessed

eventEvent-n

Services1

SOR1 SystemRecord 2

System Of Record3

Services2

Proxy API

Capid-n/v1/entity1/{id}

Capability - 1

Capability – 2

Entity1 Details View

UI App2

Entity3 Sync EventEntity Sync

Event

Page 15: Becoming the Uncarrier: T-Mobile's Digital Journey

15

Standards – Anchors, Guardrails and Self Help T-Mobile API REST Design Guidelines T-Mobile API Developers Playbook T-Mobile API Operations Playbook T-Mobile API Partner Onboarding Guidelines

Page 16: Becoming the Uncarrier: T-Mobile's Digital Journey

EASY TO ADOPT

Setting up Automated builds and deployment process. Security policies and other out of box traffic management

capabilities Framework design practice to enable reuse using build process. Generate metrics and analytics from Platform and API usage.

Winning Hearts And Minds

REQUIRED MORE EFFORT

Achieve alignment on standards and processes Achieve parallel policy executions, retries Proxy chaining limitations to an Env make it difficult to use it as a

general design pattern. Debug Trace co-relation with other APIs. Challenges from Version non-parity in on-Prem and Cloud

ARGUMENTS, CHALLENGES & CONCERNS THAT WE OVERCAME

Security in SaaS Debugging (and accepting) Time spent inside API platform REST design patterns - partnership on this front has been very

helpful.

Page 17: Becoming the Uncarrier: T-Mobile's Digital Journey

THINGS I WOULD DO DIFFERENTLY

REST guidelines – finalize early and based on what works for your organization.

Gateway scope and use clarity. Data Model and fine line between consistency and reuse CI/CD and test driven development pipeline from get go (pick one).

Lessons and Ideas

WHAT WORKED WELL

Up and running with toolset, Edge intuitiveness and simplicity to use.

Setup more optimization, transformation and design patterns. Code validation & enforcement tools. Documentation

WHERE ARE WE HEADED

Portal parity – internal and external. Digital layer harmony – striking the right balance on layer

responsibility. True API factory vision with federated API product teams operating

optimally. Drive API adoption via self serve T-Mobile Portal as well as Twilio’s

developer platform.

Page 18: Becoming the Uncarrier: T-Mobile's Digital Journey

ADVICE TO OTHER DIGITAL ARCHITECTS

Decide Layer responsibilities as early as possible. Use Hands-on approach & leverage the right platform capabilities Foster flexibility vs reuse conversation – for your organization Pragmatic standards and processes.

Imparting wisdom

ADVICE TO LEADERS

Drive organizational alignment on API and technology platform vision.

Set a clear goal on transformation journey and avoid too many direction changes.

Platform rollout is challenging – share broader vision and purpose. Help Achieve cross team synergies to build upon each others

solution – not have to solve same problem.

ADVICE TO DEVELOPERS

Continually look for optimization opportunities in frameworks and automation

Test Driven development takes getting used to – but it’s the way to go.

Operational aspect of API must be kept in mind during design. Remember, You Build It – You own it!

Page 19: Becoming the Uncarrier: T-Mobile's Digital Journey

T-Mobile Confidential

Page 20: Becoming the Uncarrier: T-Mobile's Digital Journey

Thank you