Internet Industry Search Engine

Netflix Play API: Building an Evolutionary Architecture


Jan 10, 2019 3:00 PM 1+ week ago

At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.Read more.

Search Builder

(Click to add to search box)
Search Suggestions Level 1
Play API team  Netflix Play API  Play API  API service  data architecture  data store layer  Play API architecture  Play API Service  API Proxy Service  Zuul API gateway  maximising customer engagement  service identity section  picture architecture principles  Suudhan Rangarajan  core decisions  Internet TV revolution  data sources  Evolutionary Architecture  QCon SF  utilities package  use gRPC  service team  RPC methods  Protocol Buffers  data source  Isolate Data  cache warming  microservices architecture  Patrick Kua  Rebecca Parsons  Neal Ford  computer science  data schema  request handler  service boundaries  source quotes  service identity  Daniel Bryant  Key takeaways  software engineer  business milestones  engineering impact  deployment frequency  Customer devices  API Service  book Accelerate  deployment target  peer services  Jeff Bezos  responsibility principle  
Search Suggestions Level 2
Netflix Play API  Evolutionary Architecture Presentation  Spring Boot Presentation  Cloud Foundry Podcast  Evolutionary Architecture Microsoft  API design  AI Presentation  Redaction Failure  Expose Discussions  
Search Suggestions Level 3
Play API team  Spring Boot  Consumption tier  Play API  AI systems  Azure API Management  customer journey  API service  data architecture  conference Pivotal Training  info Parliament members  mortgage origination process  loan application process  AI models  service level agreement  object storage Cloud  serverless architecture principles  AI system  EEA protection laws  Bio Asir Selvasingh  picture architecture principles  Play API architecture  object storage  scale unit approach  API end point  object storage package  data sources  data store layer  Spring Boot hero  object storage bucket  order management system  voice assistant acts  purge cache content  Zuul API gateway  software development  customer journey changes  Play API Service  whitelisting system Facebook  service identity section  Azure pricing page  Australia East regions  Netflix Play API  API Proxy Service  maximising customer engagement  Chief Executive Zuckerberg  API Management solutions  Internet TV revolution  redaction failure  Pivotal technologies  API strategy  software engineer  curated feature  Richard Seroter  United States  UK legislators  developer portal  computer science  Graph API  ERP system  microservices architecture  reciprocity principle  Facebook employees  application network  UK politicians  communication channel  software developers  development work  QCon SF  API marketplaces  voice assistant  Solution Engineering  Alan Turing  AI drive  business value  Businesses today  employee experiences  voice assistants  voice commands  AI problem  point solution  point solutions  application silos  application landscape  Senior Director  government business  UK government  UK soil  court documents  API terms  redacted text  stuff Facebook  removal petition  summary judgment  Facebook executives  Michael Vernal  filing date  Facebook attempts  API access  

**Content contained on this site is provided on an “as is” basis. 4Internet, LLC makes no commitments regarding the content and does not review it, so don't assume that it's been reviewed. What you see here may not be accurate and should not be relied upon. The content does not necessarily represent the views and opinions of 4Internet, LLC. You use this service and everything you see here at your own risk. Content displayed may be subject to copyright. Content is removed on a case by case basis. To request that content be removed, contact us using the following form: Contact Us.