This is kinda/sorta off topic, but a few quick corrections:
Optics did not come out of Kadira. Kadira was a totally separate purchase made to keep the leading Meteor based metrics solution alive, for the sake of the Meteor community and Galaxy customers. Optics was developed independently.
That being said, Optics was just shut down permanently last week. Apollo Engine is the replacement product.
Nope! MDG is just as focused inside the app as outside the app. Apollo Engine is an important product for sure, but the company strongly believes its inside the app open source offerrings are just as important. Meteor, Apollo Client, React Apollo, Apollo Server, and countless other development tools/libraries/frameworks, are still being worked on happily.
Also, Apollo Engine isn’t just outside the app. That’s a common misconception that MDG is working on clearing up. It’s important to realize that Apollo Engine isn’t just an APM tool. Sure, it monitors GraphQL API performance, handles error tracking, graphs/charts trends, handles caching, etc. All important stuff for sure, but the unique nature of GraphQL opens up many more possibilities with regards to tying and leveraging Engine directly in your development process and tools. Take a look at Engine’s recently announced schema validation features for example. The feature name doesn’t really do the feature itself justice, so I definitely recommend reading that linked to blog post. In a nutshell, you can test application schema changes against the historical GraphQL query/mutation data Engine has stored for your application, so you can decide how to effectively/efficiently make changes to your data layer, without impacting your user base. You can also wire all of this up to run via GitHub on commit, so new incoming schema changes that are being commited are compared against historical data in Engine, to look for potential issues. If you’re removing a field from your schema for example, a change that you think is harmless, schema validation will automatically check to see if people are still relying on that field in their current queries, and if so flag the issue in GitHub (so essentially GraphQL CI).
Schema validation is just one example; there are some really cool new Engine features / dev tool integrations coming down the pipe soon, that definitely blew my mind when I saw them.
Nope again! The team at MDG belives strongly in a world where a developer happiness focused company can be commercially viable, profitable, and a strong open source contributor/champion. We’re working hard to make this happen in many different areas - more details coming soon!