Road To GraphQL read and Response Chapter 2: Apollo

A few things. The first thing: “Road to GraphQL” doesn’t actually have chapters, the contents just have groupings of pages of a given subtitle. Second: I wanted to write about this second chapter/section/part of the book with the first part, but that got a lot longer than I thought it would, and this might be significantly shorter.

The section on Apollo is much shorter, maybe because it is intended to be a chapter with the introduction to GraphQL. Apollo, as covered in the first chapter and my first entry in this series, is a library that bundles additional functionality with the GraphQL specification. Apollo seems to place itself at the ready for handling the state of apps you’re building with it. In the past, developers could use Redux or Mobx in tandem with Apollo, but recently, Apollo released it’s own state store, the Apollo Link State library. And while this attempt to consolidate the needs of developers for the sake of convenience, here’s a good opportunity to talk about Apollo relative to the rest of the web dev community.

Apollo is in a perpetual state of change at the time of this post’s writing in late-ish 2019, and that can kinda be a bad thing, at least for now. As mentioned before, Apollo released it’s own data store solution for use with it’s client, but this is a big example of Apollo’s biggest problem, it’s own growing pains. Not that Apollo’s growth is inhibiting it’s ability to catch on, it’s just that everything about Apollo is pretty new, and outside of the relatively small group of developers who use Apollo day in and day out, things look pretty nebulous to those of us outside looking in. Lots of energy, new creations coalescing, but everything is still hot and new and not totally battle tested.If you are a regular listener to Syntax.fm, you may hear Wes Bos regularly talking about it, and that’s probably the first place I heard of Apollo. While Wes Bos makes it seem like it’s something that’s sorta common place (maybe for the projects Wes works on), but that certainly isn’t really the case. It will take some time for Apollo and GraphQL to catch on, and that assumes that there isn’t some new upstart thats better at doing what Apollo does with Apollo. So, while things in the Apollo system are in flux now, it’s wise not to think it’s the end all be all.

Feel free to contact me on twitter: @BxBytesSteph

Leave a Reply

Your email address will not be published. Required fields are marked *