Scaphold hits a sweetspot MDG could explore around
(There are other great offerings around the react space - I’m not promoting)
Yeah, Scaphold is great as a backend as a service. But we’re not looking to get into that industry, I’m sure they will do a great job with it. We’re working with them on a lot of Apollo/GraphQL stuff already!
Hi @dinos, I’m agree, but rethinkdb is shutdown and horizon.io will to…what’s your opinion ? I hope meteor will not face the same problem in Future…
will mongo be removed so everything related to db is up to apollo? right now I have a major issue with mongo being the default db, I need to connect to dynamo db
RethinkDB died because they made the move to monetize and experiment with different monetization strategies too late.
MDG is not making that same mistake, as far as I can tell. Hence why they’re not interested in relying on Meteor and Galaxy as their sole provider of income. They’re building Apollo and Optics.
And eventually they’ll build other services. The more income streams they’ve got coming in, the better off they are (especially in their industry).
1 Like
what’s the 1.5 release date? no info on the road map.
3 Likes
Right now, we’re focusing on things that Meteor developers have asked for, especially performance and better community involvement. That’s come at the cost of being able to spend a lot of time on better Apollo integration, but we’re happily using the two together in both of our commercial products so using Meteor + Apollo is pretty great already.
3 Likes
The biggest problem as I see for meteor right now is stagnation of it’s ecosystem. I think from business perspective it’s very important to finish this transition asap so people would know exactly how to create packages and plugins (apolo, npm, react I guess, or maybe something different) and how it all works in a coherent whole.
7 Likes
Have you ran into many issues with users of Meteor upgrading to 1.4 with Apollo? I had a horrible time trying to get Apollo to not throw errors and with 5 npm packages and the Meteor apollo package it’s really hard to tell where to even start debugging. Also does 1.5 integration look more like a 1 line package install? Currently using Apollo outside of Meteor seems to be a lot easier than using both.
4 Likes
any tentative date for the 1.5 release?
1 Like
Why is that? I would say actually using it outside of Meteor is even harder because you have to make sure to have the right build setup and accounts system setup.
1 Like
Mostly outdated docs on what deps to install (I remember like 4-5 npm installs to get it running) and then keeping NPM happy with deps… after upgrading to Meteor 1.4 broke and figuring out what needs to be updated to make Meteor happy was really time consuming. (example: Apollo breaking on 1.4.2 upgrade).
But perhaps i’m getting used to non JS package managers just working with one package ¯_(ツ)_/¯ . I think in general i’m getting tired of doing 5 npm installs for one library (and keeping them up to date). One of the nice bits about Meteor was that in general one meteor install foo was all you needed to install the foo package.
1 Like
Yeah. I think that’s just how the npm world is - I don’t think this is something bad about using Apollo with Meteor in particular.
1 Like