3 ms·
This is a garbage article. It reads as a commercial and not an informed technical piece. As I understand it, according to this article, netflix is 90% complex
by alexandercrohde 8y ago
This is a garbage article. It reads as a commercial and not an informed technical piece.
As I understand it, according to this article, netflix is 90% complex services that have nothing to do with node. All this article is describing is adding an additional layer in front of those services, which uses a hosted solution that abstracts away servers.
So it sounds like by-and-large netflix still uses traditional solutions.
So what's not clear from the article:
1. Why node?
2. Why add a layer at all? I don't see why UI A/B testing couldn't be handled with truly front-end changes. Does this somehow enable A/B tests on TV apps, for example?
3. How does this play with traditional version-control? (e.g. in a post-mortem if you need to see who changed something, and who approved it, is there a written log? And merge conflicts?)
4. Does this add a new single-point-of-failure?