My team is hiring a GraphQL support engineer. if you are interested in the role, please DM me. If you like GraphQL and helping other developers adopt it, check out the role:
jobs.netflix.com/jobs/331325157
jobs.netflix.com/jobs/331325157
Tejas Shikhare
@tejas26
I like 〽️football, skiing, politics, investing and distributed systems. Currently working on graphql at Netflix.
494 Following 390 Followers 402 Posts
Latest posts 5
Tech people on X have prejudiced view on GraphQL.
- it’s not meant to replace REST, gRPC
- it’s specifically an API style that used for building rich UIs
- it’s not a Swiss Army knife
- it’s not meant to replace REST, gRPC
- it’s specifically an API style that used for building rich UIs
- it’s not a Swiss Army knife
This is an excellent example of how to do open source well.
netflixtechblog.medium.com/a-tale-of-two-…
netflixtechblog.medium.com/a-tale-of-two-…
netflixtechblog.medium.com A Tale of Two Frameworks: The Domain Graph Service Framework Meets Spring GraphQL By Kavitha Srinivasan and Paul Bakker Thanks for the callout @InfoQ , it’s been more than but really enjoyed this experience!
5/5 ➡️ Expanding GraphQL Federation at Netflix with Tejas Shikhare: bit.ly/3TlvbYyView quoted post on X
Netflix operates a very large, #FederatedGraphQL platform. In this episode, @tejas26 explains the pros and cons of scaling GraphQL adoption.
GraphQL friends: What are your thoughts on mixing server-driven UI in GraphQL. Love to hear any best practices, learnings and success stories.