On Tue, Aug 24, 2010 at 4:35 PM, nobosh <[email protected]> wrote: > Hello, I'm a long-time ColdFusion developer looking to finally move to > something better. I've been exploring Google App Engine with DJANGO, > but haven't been blown away.
Google App Engine will also support Rails via JRuby, though I wouldn't consider it a mainstream solution, or something I would recommend to newbies. I don't see a lot of activity on Google App Engine (that could be my reading list though). Its a good solution, price competitive with a good free quota, but I think people get a bit put off by the persistence back end (Big Table). I am not overly familiar with Django, but I believe it uses the ActiveRecord pattern (just like Rails) for its persistence back end. ActiveRecord and BigTable are not a good fit apparently, so it may explain why GAE/Django development is not as popular as it should be. Google App Engine lends itself more to unopinionated frameworks which allow you more freedom for what you use in your persistence layer. i.e. Ruby/Sinatra using the BigTable APIs directly (via JRuby) might be a better fit. > I recently learned of Heroku + ROR and > find myself to be at a fork in the road. Any compelling case on why I > should go with Heroku versus App Engine + DJANGO? > Simplicity. Heroku works. It imposes the least amount of constraints on your web apps architecture: * You push code to heroku with Git * You have to use external services (e.g. S3) for writable file storage * You must have a rackup file * You must document your gem (external code) dependencies If you are making a ruby web app nowadays, you are likely satisfying most of those constraints anyway. It is common for people to push their apps to heroku very quickly and find that they Just Work (tm). Where to Heroku + ROR users go for support? If it's > these forms it's concerning that there's low activity from a newbie > perspective. In any case, I'm curious to hear your thoughts so I can > settle on a tech stack and get coding > Visit the Heroku site itself http://heroku.com the documentation is up to date and thorough. With many awkward edge cases properly documented. Its a model of how you document an unusual hosting service. -- http://richardconroy.blogspot.com -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
