Paved PaaS to Microservices
•
6 likes•3,118 views
Traditionally, a tug of war has existed between service reliability and engineering velocity. Increasing speed to fuel product innovation has meant making tradeoffs in reliability. Netflix standardizes common functionality, like service discovery, configuration, metrics, logging, and RPC across services. This frees teams to focus on the unique business value of their service. It also enables us to evolve and maintain platform components independently from individual services. Even with a standard set of components, service owners still need to combine these disparate elements into a coherent platform. We reduce this friction by providing a preassembled platform where teams only need to provide their business logic, and not worry about assembling the service from scratch. We can further streamline the service lifecycle by providing automation and tooling for development, testing, deployment and operations. We provide "one click" solutions to automatically generate the associated pipelines, machinery, and infrastructure that's required to run their service reliably in production. These patterns, while described in a Netflix context, can be broadly applicable to increase both reliability and velocity of your microservices architecture.
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Paved PaaS to Microservices
- 1. The Paved PaaS to Microservices Yunong Xiao, Principal Software Engineer, Netflix yunong@netflix.com, @yunongx, http://yunong.io June 26, 2017
- 2. 100 million customers in over 190 countries streaming 125 million hrs/day
- 3. –Wikipedia “Platform as a service (PaaS)… allows customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure and platform…” What is a Platform as a Service (Paas), Anyway?
- 4. Our Use Case
- 6. Netflix Edge API Script A Script B Script C Script D Script N … Client Library A Client Library B Client Library C Client Library N … Backend Service A Backend Service B Backend Service C Backend Service N … 1000+100
- 7. TV iOS Android Windows Browsers Discovery Playback Non- member … Backend Service A Backend Service B Backend Service C Backend Service N … Clients Standalone Services Edge API Backend Services Owned by client teams Mostly
- 10. Our PaaS to Achieving Both 1. Standardized components 2. Preassembled platform 3. Automation and tooling
- 12. What’s Inside a Microservice? RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing
- 13. Why Standards?
- 14. Mélange of RPC
- 15. Microservice Interactions µServiceClient uService µService µService µService … µService … µService
- 16. Failure: When not If
- 17. – Managers everywhere “Is it fixed yet?” Mean Time to Detection (MTTD) Mean Time to Repair (MTTR)
- 18. N Flavors of RPC µServiceClient uService µService µService µService … µService … µService
- 20. Benefits of Standardizing Consistency Leverage Interoperability Quality Support RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing
- 21. But I'm a Snowflake... Freedom Responsibility& Off-road Innovation Reintegrate BurdenVacuumNew
- 24. Getting Out of the Blocks Docs Copy/paste Which versions? Initialization Configuration Missing components Days or weeks
- 25. Velocity Reliability Product Innovation Not a single line of business logic!
- 27. Preassembled Platform RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing
- 28. Out of the Box
- 31. Insights
- 32. Application, system, and runtime metrics & logs
- 33. Consistent application, system, and runtime metrics & logs Reduces MTTD & MTTR
- 34. Configures and Initializes Correctly BOEING 747-400 NORMAL PROCEDURES CHECKLIST POWER UP / SAFETY CHECK First Officer Captain CIRCUITBREAKERS...………………...CHECKED BATTERY……………...………………….………ON STANDBY POWER………………...………..AUTO HYDRAULIC DEMAND PUMPS….………..…..OFF WINDSHIELD WIPERS....……………….……..OFF ALTERNATE FLAPS AND GEAR…………….OFF GEAR LEVER…….………….....…………..DOWN FLAPS…..……………………………....CHECKED APU….………………………………...….RUNNING ELECTRICAL SYSTEM....……SET/APU AVAIL ON APU BLEED AIR…...……………………………ON ISOLATION VALVES…………………………OPEN PACKS………………...……………………NORMAL PREFLIGHT First Officer Captain EMERGENCY EQUIPMENT…….…….CHECKED FIRE PROTECTION…………...………CHECKED INTERRUPT SWITCHES………………………ON PASSENGER OXYGEN……………..……NORMAL STAB TRIM CUTOUT SWITCHES………….AUTO TRANSPONDER…………………………………SET SOURCE SELECTORS…………………...…….SET CLOCKS…………………………………………..SET CRT SELECTORS…………………………NORMAL PFD………………………………………CHECKED ND…………………………………………CHECKED AUTOBRAKES…………………………………RTO EIU SELECTOR………………………………AUTO HDG REFERENCE SWITCH….…………NORMAL FMC MASTER SELECTOR…………………LEFT GROUND PROX SYSTEM……………CHECKED BEFORE STARTING First Officer Captain HYDRAULIC DEMAND PUMPS……………………. .............................................AUTO, AUX (1 AND 4) BRAKE PRESSURE……..……………….NORMAL FUEL QUANTITY………………..…………. ____KG FUEL SYSTEM………………………………….SET X-FEEDS…………………OPEN (1 & 4 CLOSED) SEAT BELTS SIGN………………………………ON NOTOC………………………………….CHECKED SHIPS PAPERS…………………………ON BOARD PERFORMANCE DATA......…CHECKED AND SET
- 37. What’s in and out?
- 38. Maintenance vs Convenience RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing Base Platform
- 39. Solution: Layers & Flavors Base platform Data access Rendering Backend …
- 40. How to Ensure Platform Correctness?
- 42. Dog Food with your own Service
- 43. Component Correctness Lock down versions Test components Updates require PRs Gate Keeper RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream ProcessingCustomers
- 44. How Locked Down is it?
- 46. Stay on paved path!
- 47. Season to Taste Config overrides Startup & shutdown hooks Access to 3rd party libs Swap, disable, or configure components Raw component access
- 51. 3. Automation and Tooling
- 52. Ship a Feature
- 54. Development
- 56. Env bootstrap Integrate tooling & services Run local & cloud CLI for common dev experience
- 57. Local Development Live reload Attach debugger localhost PROD
- 58. Testing
- 59. Testing
- 60. Testing Preassembled Platform RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing
- 61. Preassembled Platform Pre-Prod RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing
- 62. Provide First Class Mocks RPC Discovery Registration Runtime OS Configuration Metrics Logging Tracing Dashboards Alerts Stream Processing Preassembled Platform
- 63. Mock Data Generation RPC +
- 64. Mock Ownership RPC Discovery Registration Configuration Metrics Logging Tracing Alerts Stream Processing
- 65. Platform Testing API • Just like a runtime API, need a testing API • Provide mocks interface for components • Gets platform out of the loop for providing mocks
- 67. Deployment
- 70. Deploy and Manage Services • Pre-configured pipelines for deployment and rollback • Single command deploy to any stack • Integration for automated canary analysis • Pre-configured autoscaling
- 71. Operations
- 74. CPU profiling Core dump analysis Automated Analytics & Tooling
- 75. Our PaaS to Velocity & Reliability 1. Standardized components 2. Preassembled platform 3. Automation and tooling
- 76. The Paved PaaS to Microservices Yunong Xiao, Principal Software Engineer, Netflix yunong@netflix.com, @yunongx, http://yunong.io June 26, 2017