CODEWITHSUNDEEP
javagoogle-app-engineopenidamazon-web-servicesnutch
simpatico
simpatico

Reputation: 11087

Should I deploy on GAE or AWS?

GAE: +1 Servlet Container ready (+ JVM6) +2 openid out-of-the-box support /API -1 JPA2.0 restrictions (inc. - no criteria API) -2 I cannot use nutch

AWS: -1 I've to manage a server. -2 I've to implement OpenID myself. -3 I cannot use JPA2 with AWS.

The points above illustrate how much/little I know, esp. of AWS. Is there how I could get an AWS Java-ready, JPA2-ready, and OpenID-ready with little-hassle as is the case with GAE.

Upvotes: 1

Views: 697

Answers (2)

Juha Palomäki
Juha Palomäki

Reputation: 27032

Amazon Elastic Beanstalk provides you with a managed and scalable Tomcat environment (more app servers may be coming in future) http://aws.amazon.com/elasticbeanstalk/

Choice between AWS and GAE also depends a lot on your application. The design considerations behind the services are very much different. The goal of GAE is to provide ultimate scalability, but on the other hand eliminate fixed costs (if your application is serving only few customers, running it is very cheap).

GAE maybe be good if your application is lightweight (does not depend on heavy frameworks) and if you can adapt to the datastore limitations. For generic Java applications I would recommend AWS, if the costs associated with Beanstalk and RDS are not too high.

Upvotes: 2

tobiasbayer
tobiasbayer

Reputation: 10379

The number 1 limitation in GAE (no SQL support and thus, unbearable JPA restrictions) is gonna fall soon: Google SQL Service Preview

Upvotes: 2

Related Questions