Apollo, the industry-standard for GraphQL implementation, does not track traces for GraphQL subscriptions. Now we aren’t here to complain about Apollo, because it does do a fantastic job at providing in-depth and valuable insights into what is going on under the hood in your GraphQL deployments. However, for all the analytics it does provide, it does not currently track subscription data.
No analytics === no optimization.
Our new npm suite Aqls solves this problem.
When thinking of the 80/20 rule applied to development, what are some of your current pain-points in that last 20% of finishing a feature? I’m on a small team who for the next 5 weeks will be trying to make an open-source tool or library to help other developers. We’re thinking of focusing on GraphQL / Apollo, or possibly something to do with Vue. Onward.