Amazon Elastic Compute Cloud (EC2) vs. AWS Lambda vs. Google App Engine

Suitable for companies that are looking for performance at a competitive price, flexibility to switch instance type even with RI, flexibility to add-on IOPS, option to lower running cost with the regular introduction of new instance type that comes with higher performance but at a lower cost.

Incentivized

Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.

Incentivized

App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.

Incentivized

• Huge Diverse range of machine shapes are available which cater to our demand.
• Ability to combine the machines and integrate them with any other service in AWS (Ex: RDS, S3)
• Handling performance and scalability using auto-scaling, ELB configuration and high performance machine shapes.

Incentivized

• No provisioning required - we don't have to pay anything upfront
• Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
• Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs

Incentivized

• 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.

Incentivized

• The choices on AMIs, instance types and additional configuration can be overwhelming for any non-DevOps person.
• The pricing information should be more clear (than only providing the hourly cost) when launching the instance. AWS DynamoDB gives an estimated monthly cost when creating tables, and I would love to see similar cost estimation showing on EC2 instances individually, as not all developers gets access to the actual bills.
• The term for reserving instances are at least 12 months. With instance types changing so fast and better instances coming out every other day, it's really hard to commit to an existing instance type for 1 or more years at a time.

Incentivized

• Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
• For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
• Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
• Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.

Incentivized

• 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)

Incentivized

App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.

Incentivized

You an start using EC2 instances immediately, is so easy and intuitive to start using them, EC2 has wizard to create the EC2 instances in the web browser or if you are code savvy you can create them with simple line in the CLI or using an SDK. Once you are comfortable using EC2, you can even automate the process.

Incentivized

I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.

Incentivized

I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster

Incentivized

AWS's support is good overall. Not outstanding, but better than average. We have had very little reason to engage with AWS support but in our limited experience, the staff has been knowledgeable, timely and helpful. The only negative is actually initiating a service request can be a bit of a pain.

Incentivized

Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.

Incentivized

Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.

Incentivized

Amazon EC2 is super flexible compared to the PaaS offerings like Heroku Platform and Google App Engine since with Amazon EC2, we have access to the terminal. In terms of pricing, it's basically just the same as Google Compute Engine. The deciding factor is Amazon EC2's native integration with other AWS services since they're all in the same cloud platform.

AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions

Incentivized

We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.

Incentivized

• It reduced the need for heavy on-premises instances. Also, it completely eliminates maintenance of the machine. Their SLA criteria are also matching business needs. Overall IAAS is the best option when information is not so crucial to post on the cloud.
• It makes both horizontal and vertical scaling really easy. This keeps your infrastructure up and running even while you are increasing the capacity or facing more traffic. This leads to having better customer satisfaction.
• If you do not choose your instance type suitable for your business, it may incur lots of extra costs.

Incentivized

• Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
• Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
• Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.

Incentivized

• 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.

Incentivized