Thanks, I didn't know that. That certainly explains the high polished look of Apollo combined with the seemingly non-existent business model.
I tried Apollo Optics - horrible brand name BTW, everyone I mention it to here in Germany thinks of the eyeware retailer - and while it was easy to integrate and nice to look at, it provided little actual value compared to existing tools in the same space of performance monitoring.
Would you mind sharing what metrics and analysis are the most important for your GraphQL API? (Or what you would find most valuable if you could get it?) What tools do you use today?
The most important metrics are the traditional ones that Optics focuses on like latency percentiles and throughput. We are currently using NewRelic and Loggly. Since both the NewRelic agent and our logging system allow us to tag requests, the grouping by query structure that Optics provides, doesn't really add value. (EDIT: Further, both NewRelic and Loggly provide a better interface for zooming in on interesting areas in time.) From a operations perspective a GraphQL and a REST API aren't that different from each other that they warrant the usage of another tool.
When I tried it, the query execution view also wasn't aware of DataLoader usage. That meant, that once we started optimizing our queries, it looked like many slow parallel queries, which meant that you had to guess what was already optimized, and what wasn't.
Hi - Sashko here, manager of open source at Meteor Development Group.
We're committed long term to Meteor and Apollo both, and view both technologies as critical to the long-term success of the company. Apollo originated as a project to improve the internal data system of Meteor, but we saw that it was useful in a wider context. Today you can use Apollo with Meteor or with any other JavaScript or native mobile technology.
We decided to ship Apollo under a different name to avoid people's preconceptions that a tool released by the creators of Meteor would only work inside the Meteor platform. What we are seeing is that the JavaScript community has been consistently moving towards focused, decoupled tools, and it made sense to build Apollo in that way. Meteor has also received many improvements to make it easy to work with npm packages, new JavaScript features, etc.
I tried Apollo Optics - horrible brand name BTW, everyone I mention it to here in Germany thinks of the eyeware retailer - and while it was easy to integrate and nice to look at, it provided little actual value compared to existing tools in the same space of performance monitoring.