Great Great questions.
- Why do you feel the need to leave meteor? Is it server scaling issues? Is it the lack of community/mdg development that’s happening?
Our company and dev team is at a point to control all parts of the stack. Thats what we want to do. Its not a problem with Meteor or MDG Development. Just different wants.
From a technical point of view:
- We want to control bundling of the application to minimize page load
- We want to control our deployments
2. Also, do you feel your jump on board graphql is making the same mistake you already made?
Potentially. But the beautiful thing about GraphQL is its ability to be a middleman to your client system and backend system. As long as you approach it as that Network Trafficker, you should be able to swap these pieces in an out.
REST still exists :)