25 ms·
I’ve been reading more of the Netflix engineering blog recently (got in a clickhole), what strikes about their more recent articles as they seem to be creating
by nhoughto 6y ago
I’ve been reading more of the Netflix engineering blog recently (got in a clickhole), what strikes about their more recent articles as they seem to be creating technical solutions (like BFF and friends) for what could essentially be process or coordination problems, and that is less exciting to me.
Sometimes you don’t own the whole thing and BFF is the best way, but in my mind that place wasn’t Netflix, but some slow moving bank etc
- tpetry 6y agoI got that feeling too when reading the article. They said a common frontend for all app platforms does not work and then state they use Falcor for the android app. There is no reason they couldnt use Falcor for the ios platforms too. Looks a bit like not invented here (in this team) syndrome
- e12e 6y agoInteresting, I hadn't seen falcor before. It's a graphql alternative? Ed: was open sourced back in 2015 - discussion at the time: https://news.ycombinator.com/item?id=10075092 https://news.ycombinator.com/item?id=10075092
- jamil7 6y agoI still don't really get this, if they're using GraphQL which it appears they are with Falcor why do they need a specific microservices for every client? Can the data that each client needs not be queried ad-hoc?
- jFriedensreich 6y agofalcor uses a GraphQL alternative called jsonGraph which has overlapping features and usecases but is a completely seperate technology. The decision to have seperate services per app has nothing to do with the technology but with the politics of structuring teams and evolving technology at netflix.
- jamil7 6y agoOK, haven't read anything about falcor since it's annoucement I always assumed it was GraphQL based. So the point is to not need to wait on team X to deliver feature Y? Rather the client teams are responsible for implementing whatever they need? I think I got it.