AWS Lambda vs Google App Engine

• Lambda provides multiple methods for triggering functions, this includes AWS resources and services and external triggers like APIs and CLI calls.
• The compute provided my Lambda is largely hands off for operations teams. Once the function is deployed, the management overhead is minimal since there are no servers to maintain.
• Lambda's pricing can be very cost effective given that users are only charged for the time the function runs and associated costs like network or storage if those are used. A function that executes quickly and is not called often can cost next to nothing.

Read full review

• Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
• Flexible. We use Java for some services and Node.js for others.
• Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.

Read full review

• Putting a significant portion of your codebase into AWS Lambda and taking advantage of the high level of integration with other AWS services comes with the risk of vendor lock-in.
• While the AWS Lambda environment is "not your problem," it's also not at your disposal to extend or modify, nor does it preserve state between function executions.
• AWS Lambda functions are subject to strict time limitations, and will be aborted if they exceed five minutes of execution time. This can be a problem for some longer-running tasks that are otherwise well-suited to serverless delivery.

Read full review

• There is a slight learning curve to getting used to code on Google App Engine.
• Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
• Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)

Read full review

• I was able to perform a lot of processing on data delivered from my website and little or no cost. This was a big plus to me.
• Programming AWS Lambda is quite easy once you understand the time limits to the functions.
• AWS Lambda has really good integration with the AWS S3 storage system. This a very good method of delivering data to be processed and a good place to pick it up after processing.

Read full review

• Effective employee adoption through ease of use.
• Effective integration to other java based frameworks.
• Time to market is very quick. Build, test, deploy and use.
• The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.

Read full review