Becoming the Uncarrier: T-Mobile's Digital Journey
Download as PPTX, PDF9 likes9,720 views
T-Mobile is redefining wireless services as the 'un-carrier' by leveraging digital transformation and an API-first strategy to enhance customer experiences for over 69.4 million users. The document outlines T-Mobile's journey towards becoming a world-class digital company, emphasizing the importance of rapid delivery, security, and reusable API standards. It offers insights into their API management practices, challenges faced, and advice for other digital architects and developers in the industry.
More Related Content
Similar to Becoming the Uncarrier: T-Mobile's Digital Journey (20)
More from Apigee | Google Cloud (20)
Becoming the Uncarrier: T-Mobile's Digital Journey
- 1. ©2016 Apigee Corp. All Rights Reserved. Becoming the Un-carrier: T-Mobile’s Digital Journey Himanshu Kumar, T-Mobile Paul Williams, Apigee
- 2. ENTERPRISE IT T-Mobile’s DigitalJourney October 27,2016 T-Mobile Confidential
- 3. WELCOME
- 4. 4 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 T-Mobile Confidential Webinar Topics Breakdown
- 5. 5 5ENTERPRISE IT T-Mobile Confidential T-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.
- 6. 6
- 7. Un-carrier onthe Inside Frequencyandspeed ofdelivery ofnew capabilitiesbecomes critical forourcontinuedsuccess. Unprecedented externalintegrationandmonetization opportunities. API economyenvisioned. Self serviceAPIs forinternalandexternal consumers.Digital transformationhasbegun!
- 8. ENTERPRISE IT Digital Transformation Enablers People Process Technology Achieving API First at T-Mobile! T-Mobile Confidential
- 10. :WHY APIGEE? How it fitsin 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.
- 11. ENTERPRISE IT T-Mobile Experience Technology Landscape Scope & Guiding documents Winning hearts and minds Wins & Losses Imparting wisdom T-Mobile Confidential
- 12. 12 API Lifecycle Design Build Documentation Operate / Run Internal Developer s 3rd Party Develope rs Partner Developer s API Designers API Developers API Operators Leadershi p Experience API Capability API APIGEE EDGE Swagger API Proxy Policies Resources API Specs jso n Community Registration Documentati on Analysis APIGEE Portal Security Representation Caching Retrieval /Aggregation APIGEE Gateway Security Representation Caching PCF Spring Boot Restful APIs Capabili ty Docs Catalog Dashboards Monitoring Web / Mobile UI External Web / Mobile UI Experience API Capability API Proxy Capability API
- 13. 13 API Policies &Scope – Our Wisdom Security(authenticationandauthorization) ThreatProtection– JSON,XML,SQLInjection SLAenforcement Routing Simpledataandprotocoltransformations Payloadvalidations Consistenterrorhandling
- 14. 14 DigitalLayers Browser / DevicePresentation Server / Device Experience Apps API Gateway / Aggregation Experience API Cloud Native REST APIs Capability API Cloud Native Microservices & Data Capability App/Services Event BusEvents SOA Services Internal / External DC/Hybrid Cloud ESB SOA Services Capability Applications / Platforms DC/Hybrid Cloud System Of Record ExperienceCapability Landing Page UI App1 /v1/landing/app1/sum mary capid/v1/entity2/{id} capidx/v1/entity3/{id}/subs Capability1 entity2 Capability2 entity3 Entity- accessed event Event-n Services1 SOR1 System Record 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
- 15. 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
- 16. EASY TO ADOPT SettingupAutomatedbuildsand deploymentprocess. Securitypoliciesandotheroutofbox trafficmanagementcapabilities Frameworkdesignpracticetoenablereuseusingbuildprocess. GeneratemetricsandanalyticsfromPlatformandAPIusage. Winning Hearts And Minds REQUIRED MORE EFFORT Achievealignmenton standardsand processes Achieveparallelpolicy executions,retries Proxychaininglimitationstoan Env make itdifficulttouseitasageneraldesignpattern. DebugTraceco-relationwithotherAPIs. ChallengesfromVersionnon-parityinon-PremandCloud ARGUMENTS, CHALLENGES & CONCERNS THAT WE OVERCAME Securityin SaaS Debugging(and accepting)Time spentinsideAPIplatform REST designpatterns-partnershiponthisfronthasbeenveryhelpful.
- 17. THINGS I WOULD DO DIFFERENTLY REST guidelines– finalizeearlyand basedonwhatworksforyourorganization. Gatewayscopeand useclarity. DataModelandfinelinebetweenconsistencyandreuse CI/CDandtestdrivendevelopmentpipelinefromgetgo(pick one). Lessons and Ideas WHAT WORKED WELL Upandrunningwithtoolset,Edgeintuitivenessandsimplicitytouse. Setupmoreoptimization,transformationanddesignpatterns. Codevalidation& enforcementtools. Documentation WHERE ARE WE HEADED Portalparity– internalandexternal. Digitallayerharmony–strikingtherightbalanceonlayerresponsibility. TrueAPIfactoryvisionwithfederatedAPIproductteamsoperatingoptimally. DriveAPIadoptionviaselfserveT-Mobile Portalaswellas Twilio’sdeveloperplatform.
- 18. ADVICE TO OTHER DIGITAL ARCHITECTS DecideLayerresponsibilitiesasearlyaspossible. UseHands-onapproach& leveragetherightplatformcapabilities Fosterflexibilityvsreuseconversation– foryourorganization Pragmaticstandardsandprocesses. Imparting wisdom ADVICE TO LEADERS Driveorganizationalalignmenton APIandtechnologyplatformvision. Setacleargoalontransformationjourneyand avoidtoomanydirectionchanges. Platformrolloutischallenging – sharebroadervisionandpurpose. HelpAchievecrossteamsynergiestobuildupon eachotherssolution – nothavetosolvesameproblem. ADVICE TO DEVELOPERS Continuallylookforoptimizationopportunitiesin frameworksandautomation TestDrivendevelopmenttakesgettingusedto – but it’sthewaytogo. OperationalaspectofAPImustbekeptin mindduringdesign. Remember,You BuildIt– You ownit!
- 20. Thank you
Editor's Notes
- #4: Tamara
- #11: Why API Management - Rate of change increases up in the digital value chain, ubiquitous and self serve.
- #15: API Management layer has Provided us a toolkit to help track all API traffic from external network / customer interaction Uis crossing into API layer. Inter-microservice communication uses Gateway, where it makes sense.