1.
• Netflix – background and evolution

2.
• Netflix – background and evolution
• Monolithic Apps

3.
Load Balancer
Monolithic App
Account
Component
Catalog
Component
Recommendation
Component
Customer Service
Component
Database

4.
Time

5.
User Accounts
Shopping Cart
Product Catalog
Customer Service

6.
Product Catalog Customer Service

7.
Tipping Point
& &
Organizational Growth Disverse Functionality Bottleneck in
Monolithic stack

8.
MicroServices
Perhaps?

9.
• Netflix – background and evolution
• Monolithic Apps
• Microservices

10.
MicroService
MegaService

11.
Attribution: Adrian Cockroft, Martin Fowler …

12.
• Write programs that do one thing and do it well.
• Write programs to work together.
tr 'A-Z' 'a-z' < doc.txt | tr -cs 'a-z' 'n' | sort | uniq | comm -23 -
/usr/share/dict/words
Program to print misspelt words in doc.txt

13.
Comparing Monolithic to MicroServices

14.
Load Balancer
Monolithic App
Account
Component
Catalog
Component
Recommendation
Component
Customer Service
Component
Database

15.
Load Balancer
Account
Service
Catalog
Service
Recommendation
Service
Customer Service
Service
Catalog
DB
API Gateway
Customer
DB

16.
• Netflix – background and evolution
• Monolithic Apps
• Microservices
– Why?

17.
Your
App/Service
Service X
Service Y
Service Z
Service L
Service M

18.
• Netflix – background and evolution
• Monolithic Apps
• Microservices
– Challenges and Solutions

19.
Vs

20.
Heterogeneity
Can lead to chaos if not designed right …

21.
non-JVM

22.
Service Discovery
What’s your address?

23.
Account
Service
Catalog
Service
Recommendation
Service
Customer Service
Service
X
Service Y
Service
Z
Service
Registry
Service
(e.g. Netflix Eureka)

24.
2 Billion
~20 Billion Fan
1 Request 1 Request
Monolithic
App
MicroServices

25.
Your
App/Service
Service X
Service Y
Service Z
Cache
Cluster
Cache
Cluster
Tip: Config your TTL based on flexibility with data staleness!

26.
Your
App/Service
Service X
Service Y
Service Z
Fn {A, B, C}
Cache
Cluster
Cache
Cluster

27.
A/B Test
Service
App Service X Service Y Service Z
User Account
Service

28.
A/B Test
Service
App Service X Service Y Service Z
User Account
Service
reduces dependency
load

29.
Data Serialization Overhead
Data
transformation
getMovies() getMovie() getMovieMetadata(
)
C
l
i
e
n
t
D
C
l
i
e
n
t
C
C
l
i
e
n
t
B
Service A Service B Service C Service D
X X Avro
JSON Xml
Overall Response Time

30.
A single “bad” service can still bring your service down

31.
Your
App/Service
Service X
Service Y
Service Z
Service L
Service M

32.
Your
App/Service
Service X
Service Y
Service Z
Service L
Service M
Your
App/SYeoruvirc e
App/Service

33.
Your
App/Service
Service X
Service Y
Service Z
Service L
Service M
Your
App/SYeoruvirc e
App/Service
Service X
Service Y
Service Z
Service L
Service M

34.
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/WhatIsAutoScaling.html

35.
http://techblog.netflix.com/2013/11/scryer-netflixs-
predictive-auto-scaling.html

36.
1.

37.
Account
Service 1
Recommendation
Service 1
Customer Service
Service 1
API Gateway
Account
Service N
Recommendation
Service N
Customer Service
Service N
Customer Service
Load Balancer
Reco Service
Load Balancer
Account Service
Load Balancer
ELB

38.
Account
Service 1
Recommendation
Service 1
Customer Service
Service 1
API Gateway
Account
Service N
Recommendation
Service N
Customer Service
Service N
Account Service
LB
Recommendation
Service LB
Customer Service
Service LB
ELB

39.
http://github.com/netflix/ribbon

40.
Service Dependency Visualization

41.
Your Service
XY Farm

42.
How many dependencies does my service have?
What is the Call Volume on my Service?
Are any Dependency Services running Hot?
What are the Top N Slowest “Business Transactions”?
What are the sample HTTP Requests/Responses that had a
500 Error Code in the last 30 minutes?

43.
You
Your Service Dependency
Graph

44.
• Netflix – background and evolution
• Monolithic Apps
• Microservices
– Challenges and Solutions
– Best Practices

45.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html

46.
three

47.
Fault Injection Testing (FIT)
Device ELB Service B
Service C
Internet Zuul
Edge
Device or Account Override
Service A
Request-level simulations
Refer Re:Invent Talk “Embracing Failure: Fault Injection and
Service Reliability” – PFC305

48.
https://github.com/Netflix/SimianArmy

49.
• Netflix – background and evolution
• Monolithic Apps
• Microservices
– Challenges and Solutions
– Best Practices
• InterProcess Communication

50.
Netflix IPC Stack (1.0)
A
p
a
c
h
e
H
T
T
P
C
l
i
e
n
t
Server (Karyon)
HTTP Admin Console
Eureka (Service
Registry)
Apache
Tomcat
Client
H
y
s
t
r
i
x
E
V
C
a
c
h
e
Ribbon
Load
Balancing
Metrics
(Servo)
Eureka
Integration
Bootstrapping (Governator)
Metrics (Servo)
Eureka Integration
Registration
Fetch Registry
A Blocking Architecture

51.
Netflix IPC Stack (2.0)
Client (Ribbon 2.0)
Server (Karyon)
Admin Console
Eureka (Service
Registry)
Ribbon Transport
Load
Balancing
Metrics
(Servo)
Eureka
Integration
Bootstrapping (Governator)
Metrics (Servo)
HTTP
Eureka Integration
Registration
Fetch Registry
Ribbon
Hystrix
EVCache
R
x
N
e
t
t
y
RxNetty
UDP
TCP
WebSockets
SSE
A Completely Reactive Architecture

52.
Details: http://www.meetup.com/Netflix-Open-Source-
Platform/events/184153592/

53.
interface
@Http(method = HttpMethod.GET, uriTemplate="/users/{userId}/recommendations")
@Hystrix(fallbackHandler = RecommendationFallbackHandler.class)
@EvCache(name = "movie-rec", appName = "movieService", cacheKeyTemplate =
"{userId}")
recommendationsByUserId @Var "userId"
MovieService movieService = Ribbon.from(MovieService.class);
Observable<Recommendations> result =
movieService.recommendationsByUserId(“user1”)
.toObservable();

54.
NetflixOSS

55.
NetflixOSS
http://netflix.github.co

56.
NetflixOSS
• Eureka
• Karyon
• Ribbon
• Hystrix
• Archaius
• Servo
• EVCache
• Curator/Exhibitor

57.
Talk Time Title
PFC-305 Wednesday, 1:15pm Embracing Failure: Fault Injection and Service Reliability
BDT-403 Wednesday, 2:15pm Next Generation Big Data Platform at Netflix
PFC-306 Wednesday, 3:30pm Performance Tuning EC2
DEV-309 Wednesday, 3:30pm From Asgard to Zuul, How Netflix’s proven Open Source
Tools can accelerate and scale your services
ARC-317 Wednesday, 4:30pm Maintaining a Resilient Front-Door at Massive Scale
PFC-304 Wednesday, 4:30pm Effective Inter-process Communications in the Cloud: The
Pros and Cons of Micro Services Architectures
ENT-209 Wednesday, 4:30pm Cloud Migration, Dev-Ops and Distributed Systems
APP-310 Friday, 9:00am Scheduling using Apache Mesos in the Cloud

58.
• Netflix – background and evolution
• Monolithic Apps
• Microservices
– Challenges and Solutions
– Best Practices
• InterProcess Communication
• Takeaways

59.
http://techblog.netflix.com
http://netflix.github.io
http://martinfowler.com/articles/microservices.html
http://microservices.io/

60.
Please give us your feedback on this
presentation
Netflix Booth