AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Google Cloud Platform
Score 8.9 out of 10
N/A
Google Cloud Platform is a suite of cloud computing services used to build apps or take advantage of cloud infrastructural services, achieve legacy infrastructure modernization, or manage enterprise data and analytic needs.
$0
(25+ apps are currently available at no cost)
Huawei Cloud Network Virtual Private Cloud (VPC)
Score 7.6 out of 10
N/A
Virtual Private Cloud (VPC) from Huawei Cloud enables users to create a secure, private, and isolated virtual network. The user can customize IP address ranges, subnets, security groups, and bandwidths, and assign Elastic IP (EIP) addresses.
N/A
Pricing
AWS Elastic Beanstalk
Google Cloud Platform
Huawei Cloud Network Virtual Private Cloud (VPC)
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Google Cloud Platform
Huawei Cloud Network Virtual Private Cloud (VPC)
Free Trial
No
Yes
No
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
Google Cloud Platform
Huawei Cloud Network Virtual Private Cloud (VPC)
Features
AWS Elastic Beanstalk
Google Cloud Platform
Huawei Cloud Network Virtual Private Cloud (VPC)
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Elastic Beanstalk
7.8
28 Ratings
0% above category average
Google Cloud Platform
-
Ratings
Huawei Cloud Network Virtual Private Cloud (VPC)
-
Ratings
Ease of building user interfaces
8.018 Ratings
00 Ratings
00 Ratings
Scalability
7.028 Ratings
00 Ratings
00 Ratings
Platform management overhead
8.027 Ratings
00 Ratings
00 Ratings
Workflow engine capability
7.022 Ratings
00 Ratings
00 Ratings
Platform access control
8.027 Ratings
00 Ratings
00 Ratings
Services-enabled integration
8.027 Ratings
00 Ratings
00 Ratings
Development environment creation
7.027 Ratings
00 Ratings
00 Ratings
Development environment replication
8.028 Ratings
00 Ratings
00 Ratings
Issue monitoring and notification
8.027 Ratings
00 Ratings
00 Ratings
Issue recovery
9.025 Ratings
00 Ratings
00 Ratings
Upgrades and platform fixes
8.026 Ratings
00 Ratings
00 Ratings
Infrastructure-as-a-Service (IaaS)
Comparison of Infrastructure-as-a-Service (IaaS) features of Product A and Product B
I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -
I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
Scalability & Security comes with the service, which makes it the absolute perfect product for your business.
Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.
When most of our stuff is in Google Cloud Platform, it works great to integrate and cross/share data that is all in Google Cloud Platform or BigQuery. It has simplified things from a permissions perspective as well. I'd say it is less appropriate when trying to test something quickly locally, or when half your stuff is in AWS or another provider.
I honestly believe that it is well suited for companies, whose sole requirement is robust accessibility. Since the training part for admin takes a lot of time, I feel that it might not be suitable for small companies who are still looking to grow. Also, the product sometimes faces scaling issues and I feel like it might not be appropriate for smaller companies as they might look to expand in the future.
Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
Common application architectures can be referenced as patterns during project [setup].
Multiple environments can be deployed for an application giving more flexibility for experimentation.
Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.
The UI is so confusing. The console is good, but it is like a maze. There are too many menus and settings, and things do not work as expected. It takes time to get friendly, and it is not friendly for new users.
Support experience: Sometimes, you get a great engineer, but other times, it's very difficult to talk with them as they are unable to respond as expected and solve issues late.
Region and zone are issues, as not all services are available in all regions, which is lacking when deploying something in the same region or zone.
As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.
The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares
The Google Cloud Platform console is pretty slick for BigQuery especially. I have liked the visibility I get from using that and the way to integrate and see what's in our data lake. The logging console for tracking GKE jobs isn't quite as great, which is why it doesn't get a full 10.
As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.
- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.
We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.
Google Cloud Platform is release later than Amazon web service, I think that why Google Cloud Platform can learned and optimized the Dashboard and some features that make it easy to use and can be cheaper than amazon web service.
I'd like to point out that Huawei Cloud Network Virtual Private Cloud (VPC) is very simple to use and operate, and we can easily perform operations on it using the documents that are available on its support site. We can easily download the documents from the site, which are very useful for doing any configuration on the cloud and for operations.The security level is very good; enabling traffic and defining security rules is extremely simple utilizing their cloud portal in GUI form, which makes it simple to use, and the performance is also good; they provide a variety of solutions to meet customer needs.
It allows us to focus our efforts on other, more important items at hand
It gives us an affordable option letting me know it's available to all users, not just the largest scale ones out there
The customer service is always helpful and reliable, along with the service itself which lets me focus on my work instead of worrying about the service.