Apollo kotlin9/1/2023 3 different GraphQL Babel plugins (plus a Relay un-Babel plugin, so you can avoid using Babel for some specific cases).5 different create-* project setup packages.7 different GraphQL 'transport layers', plus a long list of link layer extensions that build on top of this.44 different server packages and apollo-server-* subpackages.In practice, "industry-standard GraphQL implementation" means 169 separate npm packages, including: Let's talk about why that is, what can go wrong, and what you should do instead. It certainly might be useful later, but on day 1 it's a trap, and you'll make your life simpler and easier if you avoid it entirely. Unfortunately, while I'm sure their platform is great, if you're setting up a fresh GraphQL API you should not start with Apollo. Apollo describe themselves as a "data graph platform" who've built the self-described "industry-standard GraphQL implementation". Nonetheless, a busy hype train & rocket-speed ecosystem means that building a GraphQL API in the real world can be a tricky balancing act of piling complex interacting components a mile high, none of which anybody fully understands.Ībout 90% of this pile is built & heavily promoted by a VC-funded company called Apollo. The fundamentals of GraphQL are remarkably simple.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |