This document summarizes key aspects of distributed architecture in a cloud native microservices ecosystem. It discusses Netflix's transition to microservices running in the cloud, key characteristics of microservices and cloud computing like scalability and availability, challenges of operating in the cloud like unpredictable failures and latency, Netflix's open source tools for discovery, circuit breaking, resilience, continuous delivery, and more. It also provides an overview of how to develop, integrate, operate, and optimize microservices in terms of embracing failures, caching, operations, and using a data-driven approach.

1. Distributed Architecture
in a
Cloud Native Microservices Ecosystem
Zhenzhong Xu

2. Real-time Data Infrastructure – Netflix
Cloud Infrastructure - Microsoft
About Me

3. About Netflix
● 2009: Monolithic -> Cloud Native Microservices
Architecture
● 2016: Completed Cloud Migration
● Today: 500+ microservices, 1000x growth

4. About Netflix
● 83M+ Subscribers
● 125M+ Streaming Hours / Day
● > 1/3 Peak NA Internet Traffic
● Thousands of Device Types
● Many Tens of Thousands of VMs
● 3 Active-Active Regions Across the World

5. Microservices
Source: Google Trends

6. What’s Important?
Availability Scalability
Agility Efficiency
Customer
Experience

7. Understanding Cloud
Multi-tenancy Scalable On-Demand Elastic
High-availability Simplified-operation Low-overhead
Low-maintnence Self-healing Fast-iterations
& Magic

8. Understanding Cloud
• Layers of >Abstractions>
• Layers of [Isolations]
• Unpredictable Failure & Latency Mode

9. Abstractions
Compute, Network, & Storage Abstractions
SaaS
PaaS
IaaS
OS
Hardware

10. Isolations
Region
AZ
Rack
Instance
VM
(Process?)
(Threads?)

11. Cloud Fallacies
• VMs and Network are stable
• Network has no latency
• Network is secure
• Bandwidth is unlimited
• Network topology is static
• Data transfer has no overhead

12. Cloud Native
• Microservice
• Immutable Infrastructure
• Decentralized CD/CI
• DevOps
• Anti-fragility
• Self-service & Automation
Availability Scalability
Agility Efficiency
Customer
Experience

13. Observe
Orient
Decide
Act CD

14. Observe
Orient
Decide
Act
Innovation
CD

15. Observe
Orient
Decide
Act
Innovation
Big Data
CD

16. Observe
Orient
Decide
Act
Innovation
Big Data
Culture
CD

17. Observe
Orient
Decide
Act
Innovation
Big Data
Culture
Cloud
CD

18. Fusion Catalyst
– Culture
• Highly Aligned, Loosely Coupled
• High Trust, High Performance
• Freedom & Responsibility
• Context, not Control
• Minimum Process

19. Cloud Native Microservices Ecosystem
Technology
CultureOperation

20. From 10,000 Feet

21. Face of Microservices

22. Stuff we built
From Operating in a Cloud Native
Microservice Environment

23. Discovery
Netflix Eureka (https://github.com/Netflix/eureka) is a RESTful service used in the AWS
cloud for locating services for the purpose of load balancing and failover of middle-tier
servers.

24. Circuit Breaker
https://github.com/Netflix/Hystrix

25. Resilience
Simian Army
(https://github.com/Netflix/
SimianArmy)

26. Continuous Delivery
Spinnaker (http://www.spinnaker.io/)

27. Configuration Management
Archaius (https://github.com/Netflix/archaius)

28. Distributed Cache
EVCache (https://github.com/Netflix/EVCache)

29. Data Pipeline
Keystone Pipeline
(http://techblog.netflix.com/search/label/keystone)

30. Monitor & Alert
Atlas (https://github.com/Netflix/atlas)

31. Active-Active Regions

32. Microservice Ecosystem
● More: https://netflix.github.io/

33. How to
Develop, Integrate, Operate, and Optimize
a Microservice

34. Build a Microservice
Optimize for Speed. Fast iterations.

35. Build a Microservice
Polyglot technologies

36. Build a Microservice
● Highly Aligned, Loosely Coupled
● Freedom & Responsibility
● Context, not Control
● High Trust, High Performance, Minimum Process

37. Integrate a Microservice

38. Discovery
Devices
Internet
ELB
Proxy
API
Discovery
Microservice A
Microservice
Microservice
Microservice
Microservice
Microservice
Public IPs
Private IPs

39. Devices
Internet
ELB
Proxy
API
Discovery
Microservice A
Microservice
Microservice
Microservice
Microservice
Microservice
Microservice B

40. Embrace Failures
● Assume all failure modes
● Circuit breaker

41. Embrace Failures
● Chaos Engineering
○ Instance termination
○ Zone partitioning
○ Region evacuation
● Limit Blast Radius

42. Embrace Failures
This means states need to be available across
all regions at any point of time.

43. Cache Replication
Eventual consistent replication protocol

44. Operate a Microservice

45. Operations
● Automatic Deployment
● Monitoring & Alertings
● DevOps
● On-call

46. Optimize a Microservice

47. Optimize a Microservice
● Incremental features
● Data driven
Observe
Orient
Decide
Act CD

48. Questions?