6 ms·
Google App Engine for Java is another PaaS option for running Java in the cloud. I wonder how these two compare?
by protagonist_h 15y ago
Google App Engine for Java is another PaaS option for running Java in the cloud. I wonder how these two compare?
- aphexairlines 15y agoalso Amazon Elastic Beanstalk.
- edvinasbartkus 15y agoalso CloudFoundry (still Beta though)
- tomas_lin 15y agoElastic Beanstalk is also available in US_East region. If your company is not based there, you end up getting fairly unmanageable lag. CloudFoundry Beta has some really bad limitation right now, ie. no pricing, cannot assign point an external domain name, etc.
- tomas_lin 15y agoGoogle App Engine has a fairly restrictive Java implementation. It means that most libraries that you are familiar with would likely not work there. So you can't really just take a war file that works somewhere else and stick it on App Engine. They do provide a few nice built-in service like image manipulation. The problem with services like Cloudbees and Amazon's Elastic Beanstalk is that you end up updating an entire war file that you build locally. This can take a long time. Cloudfoundry only serves up deltas, but you still end up having to build the entire war file on your local machine ( at least for Grails ). Heroku's approach seems much nicer, you get some initial setup pain, but then you can just use a standard git workflow.
- SachaLabourey 15y agoTomas, this is not true, at least with CloudBees you have a delta deployer that makes it a breeze to update your applications as it just sends the delta from the last upload!