SpringOne Platform 2017 Brendan Aye, T-Mobile T-Mobile wanted Cloud Foundry, and they wanted it quickly. The target was an application receiving 12 million daily calls running on the platform in three months. With no IaaS and complicated politics, were they able to meet their deadline? This talk will focus on some of the unexpected problems (technical and otherwise) that you may encounter in a large enterprise and how to address them.

1. Zero to 12 Million
Brendan Aye and James Webb
1

2. What Were We Trying To Solve?
2
Time and energy to deploy were at an all time high
7 months and 72 steps
to get code out the door
Environment configuration &
stability
Infrastructure scaling
was a problem

3. Microservices for
smaller, more
manageable
deployments
Shift to DevOps
You code it,
you own it!
Environment
Consistency
Fail Fast / Fix
Fast
On-Demand
Elasticity
Why Pivotal
versus open
source?
SUPPORT
Expert guidance &
troubleshooting
ARCHITECTS
Microservice adoption
help
RESOURCES
Faster than starting
from scratch
Why Did T-Mobile Choose Cloud Foundry?

4. Networking was our
biggest hurdle;
Pivotal did not
initially support
our network layout
No on-premise
S3 object storage
RabbitMQ and
MySQL were a must (but
being multi-tenant makes
a bad neighbor bad)
Existing processes did not
support rapidly evolving
monitoring
requirements
T-Mobile’s infrastructure resources were established to support teams
developing monolithic applications on stateful servers.
Challenge #1 - Technology
4

5. How did we overcome
these technology
challenges?
 Manual BOSH deployments of
services that didn’t support multi-
subnet to enable Spring Cloud
Services
 Created a BOSH release for
LeoFS – an open source, S3-
compatible object storage
 We decided to not offer
RabbitMQ or MySQL at launch
 Leveraged DataDog for self-
service monitoring
5

6.  We did not fit into the existing compliance
processes/paradigms
 Cross-organizational executive
sponsorship
 Wildcard certificates configuration
 Education and patient communication for
security exception for wildcard certs
 Lack of automated provisioning for
necessary resources
 Control your own destiny… if your platform
depends on it, take ownership!
The Challenge? The Fix?
Challenge #2 - Process
6

7.  DevOps culture not being practiced
 Alignment of our first dojo helped set the
stage for DevOps
 Fear of eliminating future job
responsibilities
 Training for teams to understand roles
created by new technologies
 Developer learning curve for cloud-native
apps
 We hosted many PCF101 sessions for all
areas to gain expertise
 Office politics
 Sponsorship from C–level, VPs and
directors have helped eliminate
Challenge #3 - People
The Challenge? The Fix?
7

8. Before we began with Cloud Foundry
A Java monolith with
1000+ functions running
on WebLogic
Scaling up GetUsage required
scaling the entire app, and the 7
months and 72 steps it required
One function - GetUsage –
took
12 million daily calls
So How Was Our First App Launch?
8

9. Within 3 months after starting platform installation
Rebuilt GetUsage as
a Spring app
Fixed a bug same-
day with zero
downtime
Auto-scaling to meet
demand with no
human interaction
Taking 100%
of production
traffic in PCF
DevOps team is now
happy and well-
rested!
So How Was Our First App Launch?
9

10. Platform Adoption
0
2,000
4,000
6,000
8,000
10,000
12,000
17-Aug-16
31-Aug-16
14-Sep-16
28-Sep-16
12-Oct-16
26-Oct-16
9-Nov-16
23-Nov-16
7-Dec-16
21-Dec-16
4-Jan-17
18-Jan-17
1-Feb-17
15-Feb-17
1-Mar-17
15-Mar-17
29-Mar-17
12-Apr-17
26-Apr-17
10-May-17
24-May-17
7-Jun-17
21-Jun-17
5-Jul-17
19-Jul-17
2-Aug-17
16-Aug-17
30-Aug-17
13-Sep-17
27-Sep-17
11-Oct-17
25-Oct-17
8-Nov-17
22-Nov-17
10
MicroService
Mandate
CloudFoundry as a
Strategic Growth Platform
Critical
Mass
Users selling our platform
and answering each
others
questions
Retail
Season
Scaling applications to
meet forecasted demand
1,000AIs
3,000AIs
11,000AIs

11. 11
What affect did it have on the Business?
Faster apps
43% reduction
in application response
time
More frequent
changes
40% increase in planned
changes
Fewer and shorter
incidents
83% fewer incidents,
resolved 67% faster

12. Use Slack for
Centralized
Communication
Control
your own
Destiny
Monitor
Everything
you Care About
Executive
Sponsorship
Fight
for What
Matters
Branding
and Sales
What’s Important?
12

13. Q&A
13

14. THANK YOU!
14