4 ms·
It also depends on MongoDB as your sole backend database. I played with Meteor when it came out and I concur maybe Meteor is OK for prototypes but for somethin
by tedchs 12y ago
It also depends on MongoDB as your sole backend database. I played with Meteor when it came out and I concur maybe Meteor is OK for prototypes but for something production ready I'd rather just use Angular + Google App Engine + Google Cloud Endpoints.
- phpnode 12y agoI'm curious about your choices here, I would not really trust MongoDB with my data for a few reasons, but at the same time, building on Google's services seems even more risky - if they shut down those services (which is not inconceivable), you'd be facing a pretty nasty rewrite + migration to a new platform.
- goldenkey 12y agoKind of silly that you wouldn't use MongoDB yet you'd use GAE. GAE is a turd, Google has been struggling to compete in the cloud business and failed to come out with any value. You get locked into a Heroku-like platform with awful performance, awful stability, and arcane quotas. http://www.carlosble.com/2010/11/goodbye-google-app-engine-gae/ http://www.carlosble.com/2010/11/goodbye-google-app-engine-g... http://3.14.by/en/read/why-google-appengine-sucks http://3.14.by/en/read/why-google-appengine-sucks
- extraeee 12y agoThose two links are to articles written 3+ years ago. I'd be interested to see more recent experiences.
- tedchs 12y agoThanks for the feedback. I would encourage you to note that those blog posts are from 2010 and 2009, and my understanding is the platform has improved dramatically in the ensuing 4-5 years. I'm a Linux systems engineer, but for an app where I'm not going to admin my own infrastructure, I have been happier with App Engine than other PaaS options.
- goldenkey 12y agoNo competent Linux admin would use a PaaS. I find it very hard to believe that you'd rather use GAE instead of a virtual dedicated.