SpringOne Platform 2018 Real World Transformation Experiences at StubHub George Loyer, StubHub

1. StubHub’s Enterprise
Modernization Journey
SpringOne Platform by Pivotal
Presented by:
George Loyer
@gloyer

2. 2
Who are we?
At StubHub, we’re fan first in everything we do.
Millions of tickets
sold per month
across 48
countries.
100 Million
unique visitors
every year
Delivering
tickets in paper
and electronic
form
Honoring the
Fan Protect
Guarantee
A ticket is sold
on StubHub at
an average of
one every 1.3
seconds
1.3sec

3. 3
THE STUBHUB
MODERNIZATION OPPORTUNITY
Change the way we deliver products to our fans
Increase our use of data to further personalize the fan experience
Increase our agility to radically increase the number of experiments we do
Accelerate our move to the public and private cloud
Double-down on our focus on the fan journey from beginning to end
1.
2.
3.
4.
5.
Ops, Architecture, Developers, and Business Owners
all had challenges to deliver this modernization.

4. 4
Fears about Modernization
</>
Loss of experts
when automation
replaces humans
Re-architecture
must be reflected
in organization –
no control over org
Re-architecture
threatens well-
defined traditional
team scopes
Poorly executed,
modernization
takes resources
and doesn’t
return improved
agility
OPS ARCHITECTURE DEVELOPER BUSINESS OWNER

5. 5
REDUCING RISK =
REDUCING FEAR
Reduce risk by delivering
platform and first apps as
demonstrations
Private, cloud-first in a
familiar environment, GCP
cloud as experience gained
First apps uncover
challenges in CI/CD and test
automation – home page
Ramp up more teams after
modernization sequencing
Inventory search, front-to-
back checkout scenario
Learn more about running
apps on the platform in
production
Full team deployment
across all bounded contexts
Hybrid deployment enabling
flexibility for incremental
transformation of
applications
CRAWL WALK RUN

6. 6
THE OPERATIONS STORY
CHALLENGES SOLUTIONS
▪ Private data center over
deploys resources to meet
peak demands
▪ Ops team required to make
all changes in production
and dev infrastructure
▪ Each Ops specialty is a
gate for a product to get
into production
▪ PCF platform as a service
(PaaS) in private data center
▪ PCF in Google Cloud
Platform (GCP) to form a
hybrid cloud deployment
strategy
▪ Auto-scaling microservices
clusters to drive higher
machine utilization
▪ Automating all things
▪ Automating services so that
there are no tickets to get to
production

7. 7
THE ARCHITECTURE STORY
CHALLENGES SOLUTIONS
▪ Applications are not cloud
native
▪ Microservices-architecture
supplanting services-
architecture
▪ Domain organization fails
bounded-context tests
▪ Application transformation best
practices to implement brown
field cloud native
▪ Application dojo engagement to
implement green field cloud
native apps
▪ Enterprise architecture
engagements to define clean
bounded contexts
▪ Modernization forum led by
engineering to prioritize and
sequence targets
▪ Hybrid deployment to solve WAN
latency issues during early
phases

8. 8
THE DEVELOPER STORY
CHALLENGES SOLUTIONS
▪ No self-service access to
the platform resources
▪ No full CI/CD automation,
requires humans as
services
▪ Missing or failing test
automation requires QA
gate to manually test
Concourse pipeline CI/CD automation
▪ Template from platform, pipeline
customization owned by
engineering
SDLC gate automations
▪ Test driven development
practices, highly reliable
automated test suites
▪ Self-service InfoSec tools for
validating code security (static
and dynamic)
▪ Code review and architecture
review assistance automated</>

9. 9
THE BUSINESS STORY
CHALLENGES SOLUTIONS
▪ Long design and
development cycles
▪ Long release cycles with
many manual gates
▪ Hard to do fast experiments
▪ Bounded context and cloud
native design reduce cross-
team coordination
▪ Pipeline, test and compliance
automation eliminate the
ticket-queuing tie up
▪ Shorter time from Idea-to-
Production allows more
experiments
▪ Blue-green deploy per
microservices cluster reduces
cross-team coordination

10. 10
LESSONS LEARNED
EACH LAYER ADDS VALUE
</>
Automating ops with
PCF and Bosh frees
capital spend
Identify these
opportunities where
Ops is over-deploying
to reduce risk
Self-service and auto-
scaled infrastructure
create re-architecture
value
Increasing developer
velocity helps pay for re-
architecture while
delivering value
Hybrid deployment
allows services to
incrementally move to
microservices
Find a way to transition
to the new architecture
without a Big Bang
SDLC automation
eliminates human gates
and enables shorter
Idea-to-Production
Emphasize value to the
business, not tech value
(also there)
OPS ARCHITECTURE DEVELOPER BUSINESS OWNER
Multi-dimensional value drives the decision forward with greater enterprise commitment

11. 11Source: Place footnote and source information in this area.
VALUE DELIVERED
▪ Platform operational in our Data Center
▪ Storefront (home page) Application running with canary traffic
in production
▪ Platform operational in Google Cloud Platform (GCP)
▪ Search Events application modernizing, breaking one of
several monoliths
▪ Checkout modernizing, moves key flow to high velocity
experimentation platform
▪ Mobile Ticket Transfer modernizing, makes high pain point
experience available for high velocity experimentation

12. THANK
YOU!!