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
Proxmox VE
Score 8.9 out of 10
N/A
Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC. Users can manage virtual machines, containers, highly available clusters, storage and networks via a web interface or CLI. Proxmox VE code is licensed under the GNU Affero General Public License, version 3. The project is developed and maintained by Proxmox Server Solutions GmbH.
$7.50
per month
Pricing
AWS Elastic Beanstalk
Proxmox VE
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Community
€ 90
year & CPU socket
Basic
€ 280
year & CPU socket
Standard
€ 420
year & CPU socket
Premium
€ 840
year & CPU socket
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Proxmox VE
Free Trial
No
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Proxmox Virtual Environment's source code is published under the free software license GNU AGPL, v3 and thus is freely available for download, use and share. A Proxmox VE Subscription is an additional service program that helps IT professionals and businesses keep Proxmox VE deployments up-to-date. A subscription provides access to the stable Proxmox VE Enterprise Repository delivering software updates and security enhancements, technical help and support.
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
Proxmox VE
Features
AWS Elastic Beanstalk
Proxmox VE
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Elastic Beanstalk
8.8
29 Ratings
9% above category average
Proxmox VE
-
Ratings
Ease of building user interfaces
8.919 Ratings
00 Ratings
Scalability
8.329 Ratings
00 Ratings
Platform management overhead
8.928 Ratings
00 Ratings
Workflow engine capability
8.323 Ratings
00 Ratings
Platform access control
8.928 Ratings
00 Ratings
Services-enabled integration
8.928 Ratings
00 Ratings
Development environment creation
8.328 Ratings
00 Ratings
Development environment replication
8.929 Ratings
00 Ratings
Issue monitoring and notification
8.928 Ratings
00 Ratings
Issue recovery
9.426 Ratings
00 Ratings
Upgrades and platform fixes
8.927 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.
We used Proxmox to implement private cloud services, for clusters of a small number of servers, from 3 to 11 with and without high availability. Allways with ZFS file systems, and we used to install the root pool in SSDs mirrored and use other pools with RAID 10 in groups of four, for the virtual machines and containers, for the backups and snapshots, we used magnetic disks with RAID 10, in groups of four. Do not use an even number of servers because does not facilitates the implementation of High Availability, because the corosync service must have an odd number of servers to detect a failed server for the quorum system. We used a variety of servers, from clone PCs with AMD Ryzen with 6 cores and 12 threads with 64 GB of RAM no ECC, to high end servers with 64 cores and 128 threads per cpu and 2 cpus per server, with AMD EPYC Rome or Milan, 2 terabytes of RAM ECC.
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 web UI does not work as well on mobile devices. It is useable, but a mobile optimised / responsive UI would be nice to have. There is a mobile app, so that may alleviate this issue, but I have not yet tried it.
Support in the community forums could be better. There are paid support plans, but new users trying out the software will not have access to this. Answers to questions can sometimes be terse, and I can imagine this may put some people off.
The wiki is a bit hit and miss with certain topics. I've often seen outdated or missing information, and the whole thing looks like it could do with some polish. I'd love to see it opened up for the community to add to.
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.
Proxmox VE provides the most capable, yet stable virtualization platform in the market today. Licensing options are also competitive and cost-effective for support, and support is extremely fast and knowledgable of getting issues resolved as quickly and soundly as possible.
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 interface is easy to use for most of it, but still lacks screens for some configurations. Also, a few of the screens are not as intuitive as they could be. This is specially true with disk and network configuration, where some graphic/visual representations of the configurations would be very useful
Proxmox VE's ha-cluster functionality is very much improved, though does have a not-very-often occurrence of failure. In a 2-node cluster of Proxmox VE, HA can fail causing an instance that is supposed to migrate between the two nodes stop and fail until manually recovered through the command-line tools provided. Other than this, the HA clustering capability of Proxmox VE has proven to be reliable in 3 or more clustered environments with much less chance of these failures to occur.
Proxmox VE's interfacing is always fast to load, both the Web interface and the command-line tool interfaces. Reporting is practically real time almost all the time, and you can see everything in mere seconds, easily able to identify if something is wrong or it everything is in tip-top shape as always desired
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.
Proxmox VE is cheaper than VMware, especially upscaling an HA architecture. Compared with other free or less expensive solutions, Proxmox VE is high compatible with more types of hardware solutions and more VM types. From my point of view, Proxmox VE has no competitor at the same price level, it offers the most complete and production-ready HA solution.
Proxmox VE provides everything you need to quickly add new storage mediums, network and local, as well as networking interfaces, such as using Linux standard bridges and now Open-vSwitch bridges which can be even more scalable than before. Proxmox VE 4.0 dropped support for OpenVZ in favor of the more well supported and native LXC and made an upgrade path to it very simple.