AWS Elastic Beanstalk vs Proxmox VE

• AWS Elastic Beanstalk was easy to implement, we only had to insert the application code to have it up and running in a few minutes. This helps us to launch company campaigns for different areas such as marketing, commercial and human resources.
• It has a fast learning curve, since the training material of the platform is public on the manufacturer's portal, furthermore it is easy to interact and intuitive for developers.
• The productivity of the equipment is optimized since they are not worrying about preparing the platform or infrastructure, they only have to attend to what is required by the application and its operation and this maintenance.
• The indicators and metrics that it has, ensure that the application cannot be saturated and have a performance problem, with AWS Elastic Beanstalk the application can scale resources when needed automatically.

Read full review

• ZFS storage out of the box. The integration with ZFS is fantastic. You can easily create pools to store your VM images and data on, and the Proxmox web UI provides an easy way to check drive health, ZFS scrub status, etc.
• Great web UI. Practically everything configurable is available to do so from the web user interface. You'll rarely need to drop to the command line for administrative tasks, unless you want to, in which case you can do that too. The UI also provides graphs and visualisations to help you keep check of how everything is performing.
• Easy to setup a high availability cluster. Although Proxmox VE works perfectly well on a single server, you can also install it on multiple hosts and setup a cluster.
• Uses a Debian core system with an Ubuntu based kernel. This means everything to do with the base operating system is tried and trusted. We use a lot of Debian and Ubuntu installs, so having this run underneath Proxmox VE was an added bonus for us.

Read full review

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

Read full review

• Can't manage ZFS replication or snapshots as easily as I'd like
• Encrypted disks aren't easily deployed in VMs
• Moving disks between VMs is not automated

Read full review

• Greatly reduced time in setting up and deploying test environments has saved a lot of hours and money.
• Near-zero maintenance means that we don't spend any time tending to servers, the app containers just work.
• The initial learning curve is a little steep to get services hosted in Elastic Beanstalk talking to external services like Redis, MongoDB, etc; but once one understands the pattern, development is a breeze.
• The command line interface has enabled us to build many utility scripts that simplify our development workflow, thereby saving time.

Read full review

• It's a great solution allowing you to use all the server's resources on a single platform, saving energy, network resources and trouble of not having access to a troubled system. The ROI is immediate!
• Very secure system, allowing you to run your firewall directly on this system. Again immediate ROI.

Read full review