Over the past month, Netflix has been sharing stories from the API optimization effort that started a little over a year ago. The initial focus[1] of the performance optimizations was to reduce chattiness and the payload size but over the course of the year, as a result of the redesign, API development and operations was distributed and the services layer became asynchronous. The primary redesign feature was redefining the boundary of client and server responsibilities[2] to enable fine grained customizations such as content formatting to address the differences(memory capacity, document delivery and models, user interactions etc) among the various client devices that connect to Netflix.
««
Next »
« Previous
-
Here’s (one of the reasons) why Scala is awesome -
Lambdas vs. Closures
-
Why Don’t Software Developers Use Static Analysis Tools to Find Bugs?
-
Moving from Partial Views to AJAX Calls
-
Setting up Static and Dynamic (LACP) Link Aggregation (802.3ad) on D-LINK DES-3526/DES-3550 using the CLI.
-
Replicate or copy a database table with PHP
-
Tourist.js
| Subversion | |
| Written by: Lorna Jane Mitchell | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
Add your comment
