I donβt think there is another alternative (with respect to code portability) to GAE right now, since GAE is in its own class. Of course, GAE is cloud computing, but I see GAE as a subset of cloud computing. Amazon EC2 is also cloud computing (as well as Joyent Accelerators, Slicehost Slices), but obviously they are two different beasts. So now you are in a situation that requires a rethinking of your architecture, depending on your needs.
The immediate benefits of GAE are that it is essentially maintenance free, as it is infrastructure-related (scalable web server and database administration). GAE is more suited to those developers who want to focus only on their applications, and not on the underlying system. To some extent, you may consider the developer to be friendly. Now it should also be said that these other cloud computing solutions also allow you to only worry about your application as much as you need by providing VM images / templates. Ultimately, your needs will dictate the approach you must take.
Now, with all this in mind, we can also create hybrid solutions and workarounds that could also satisfy our needs. For example, GAE does not seem to be suitable for this particular application that you need to describe. In other words, GAE offers a relatively large number of requests, a low number of processor cycles (not sure if the paid version will be different).
However, one way to solve this problem is to create a custom solution that includes GAE as an external interface and Amazon AWS (EC2, S3 and SQS) as a backend. Some will say that you could also build your entire stack on AWS, but this may include rewriting a lot of existing code. In addition, as a workaround, the previous postoverflow post describes a method for simulating background tasks in GAE. Alternatively, you can look at HTTP Map / Reduce to distribute the workload.
Fuentesjr Oct 01 '08 at 1:58
source share