Who better to talk about microservices — one of the hottest technology trends for 2016 — than Netflix? This streaming-entertainment giant began adopting them in 2009, years before the exact term even existed. Join MuleSoft and Netflix as they co-present the value that a microservices architecture can bring to your business, and see first hand the real-world implementation of APIs at Netflix. Then learn from MuleSoft’s CTO how APIs and DevOps are two important pillars of microservices and discover how they can become part of your application network.
6. No business is safe from disruption
6
“52% of the Fortune 500
have been merged,
acquired, gone
bankrupt or fallen off
the list since 2000.”
– R. Ray Wang, Principal Analyst, Constellation Research
7. But some survive and thrive
7
McDonalds: just a fast-food chain?
a digital restaurant platform
for
innovation and execution agility
8. What are they doing right?
8
on what: better apparel? price and selection?
Under Armour is
“building the biggest connected fitness platform in the world”
competes with
9. They are composable, built for change
9
an immersive content platform
automotive software innovation platform
parcels and logistics API-first business
retail enterprise data fabric
network as a service
10. Remember why an application network
10
A seamless network of applications that…
… is organized around focused,
well-defined units of value
… is recomposable
… emerges bottoms-up
via self-service
… where visibility, security and
govern-ability are built in
… where connectivity and reuse
are top-level concerns
… bends, not breaks
… where each node adds value
to the whole network
… where the business regains
control of its future
12. 12
The 2 pillars of microservices
API
excellence
devops
excellence
13. The 2 pillars of microservices
• API excellence
- Define atomic service boundaries
- Design for purpose – know service commitment
- Dependencies well-defined and managed
- API lifecycle
• Devops excellence
- Standardize containers and meta-services (services for your
services)
- Automate promotion, testing, provisioning, deployment, security,
…
- Design for resilience and operatability
13
14. Services at Netflix
Self-contained functionality exposes an API
Always owned by a team
Many teams own more than one service
Operated by owner team
Self-contained functionality exposes an API
Always owned by a team
Many teams own more than one service
Operated by owner team
24. Operations: engineers are responsible for:
Code pushes
Metrics, alerts, monitoring
Choosing the right tooling
for whatever operational
insight you need
27. How to create a new service - paved path
Teams want to build
business logic, not an RPC
mechanism
A central team can provide
a paved path (template)
28. 28
Lessons from microservices at scale
Smart enablement:
• Templatize services
• Templatize process
• Reuse: patterns
• Reuse: services
• Provide expertise
Smart operations:
• Automated++
• Fail fast & learn
• Design for failure
• Disrupt yourself
• Bend vs break
Smart containers:
• Built-in governance
• Built-in meta-svcs
• Setup for SDLC
• Fungible
• Understood by ops