Ask HN: Were you happy moving your API from REST to GraphQL?
Mostly, NOTE: I'm using python/django/graphene server side and apollo client side.<p>I <i>love</i> how flexible it is for client developers and because the great client side libraries it helps to eliminate a ton of boiler plate code on the client side.<p>My biggest complaint has been "lost" exceptions and caching.<p>Because it's possible for an exception to be thrown server side on one field while the other ones succeed I've been plagued with hard to monitor/find errors. I ended up writing a shim to parse the response in an attempt to get more insight into #errors / fields (this has also been really helpful for monitoring slow queries in new relic since all requests go to the same endpoint which breaks a ton of APM monitoring).<p>My other issue has been around caching, in apollo there are ways to say "don't use the cache for this request", but it's not to give an object a cache ttl. My app allows users to search for events that are happening near them right now, and I've run into several issues where apollo decided that an event from yesterday should be added to a result. It happened frequently enough even with queries that included times as an argument that I ended up basically implementing a "middleware" between what apollo gives back and the component, which felt really ugly.