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
VMware vSphere
Score 8.0 out of 10
N/A
An enterprise workload platform, vSphere is used to improve the performance for a data center. It is used to boost operational efficiency, supercharge workload performance, and accelerate innovation.
$995
per year
Pricing
AWS Elastic Beanstalk
VMware vSphere
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Standard
$995.00
per year
Enterprise
$3,995.00
per year
Offerings
Pricing Offerings
AWS Elastic Beanstalk
VMware vSphere
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
VMware vSphere
Features
AWS Elastic Beanstalk
VMware vSphere
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
VMware vSphere
-
Ratings
Ease of building user interfaces
8.018 Ratings
00 Ratings
Scalability
7.028 Ratings
00 Ratings
Platform management overhead
8.027 Ratings
00 Ratings
Workflow engine capability
7.022 Ratings
00 Ratings
Platform access control
8.027 Ratings
00 Ratings
Services-enabled integration
8.027 Ratings
00 Ratings
Development environment creation
7.027 Ratings
00 Ratings
Development environment replication
8.028 Ratings
00 Ratings
Issue monitoring and notification
8.027 Ratings
00 Ratings
Issue recovery
9.025 Ratings
00 Ratings
Upgrades and platform fixes
8.026 Ratings
00 Ratings
Server Virtualization
Comparison of Server Virtualization 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.
vSphere is well suited for multiple VMWare hosts and can be very useful in larger enterprises where vMotion is used to load balance and failover running virtual machines. In smaller businesses with one or two hosts then the features can be overkill. The addition of virtual TPM support is a very nice addition to provide vm security in a more Microsoft supported methodology.
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.
More detail in recent tasks. Instead of just showing a task called "Reconfigure virtual machine" also have a link to more detailed information as to what was reconfigured, changed or removed.
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.
We are constantly looking for change that will benefit our company. We are not ones to stick with a product simply because it is what we know, but rather looking for what fits us best. We can't imagine another product on the market today doing a better job of handling our infrastructure than vSphere.
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
Very useful for environments where space and energy consumption are issues and management is not very keen on upfront spending on hardware every time whenever requirement comes from any dept for provisioning a machine for their occasional use, easily can be done in case of VMware vSphere in few clicks. Backup, security, monitoring and management everything is covered but at additional cost.
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.
I rarely ever have to contact support and when I do need to resolve an issue, there is always an abundance of kb articles and research information available that can help quickly resolve the issue. Depending on the type of support contract you have, you may get support from some offshore group in another country and this could be a little challenging because of the language barrier.
- 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.
Just make sure that when you implement, that the person implementing truly knows what they are doing and has a plan of action coming in. Since our initial implementation using a consulting service, I have implemented a few vSphere just from what I learned at the initial implementation and use over time, and the person implementing really needs to know what they are doing or you will miss out on features that may help you down the line
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.
vSphere has a lot more feature sets than Hyper-V but at a much higher cost of entry versus MS Hyper-V. I have not been able to play with Hyper-V as much as I would have liked, but the setup and ongoing maintenance seems to be easier in vSphere than with Hyper-V
The contract terms are very clear and can be updated as per the project requirement. Customer support is also included in the contract which help us to troubleshoot critical issues very easily. Training included in contract will really help the client team to empower and hands-on on the latest updates and enhancements
As I said earlier, they're always ready to understand our issues and propose the best and most appropriate solution for issues all the time. The security patches solution is accordingly to the business needs. Another scenario is their Knowledge Base where they're many articles that help you in order to solve something which is wrong.
Having vSphere helped my business quickly recover from a ransomware attack which would have crippled us for weeks if we were not virtualized. I think the ROI on something like that is immeasurable.
vSphere has allowed my company to purchase bigger server hardware to host 3 or 4 virtual servers, which was at a cost much lower than buying 3 or 4 server hardware boxes, saving us thousands each time we need to upgrade hardware.