3 ms·
To be fair, Google AppEngine gives you that same ability. The difference is, you have to build your app for AppEngine rather than building a plane jane vanilla
by mrkurt 17y ago
To be fair, Google AppEngine gives you that same ability. The difference is, you have to build your app for AppEngine rather than building a plane jane vanilla rack/rails/sinatra/whatever app with postgres.
The app I have running on Heroku uses a number of prebuilt gems, including things like twitter-auth that sort of assume you're using migrations and ActiveRecord with it. I may move it over to AppEngine at some point, but the absolute fastest way for me to get an app up and running was with Heroku.
- knowtheory 17y agoYou're not entirely correct on that point either. The goal that i have as someone who's building tools for GAE, is to sufficiently abstract the GAE tools so that you aren't building specifically to AppEngine's infrastructure. DataMapper is a great example of an abstraction layer that allows you to build application code that is portable across infrastructure. The goal is to be able to build an application on GAE, and if your requirements change at some point and GAE doesn't fit, you can migrate off of it without substantial pain.
- knowtheory 17y agoAdditionally, it's pretty quick to get an application up and running on GAE as well. Not entirely trivial at the moment, but it's getting close (still waiting on the release of a couple gems before i can say that's the case). If you want to see one way to get an application up and running here's one: http://code.google.com/p/appengine-jruby/wiki/GettingStarted http://code.google.com/p/appengine-jruby/wiki/GettingStarted