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
AWS Lambda
Score 8.3 out of 10
N/A
AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
VMware ESXi
Score 7.1 out of 10
N/A
A bare-metal hypervisor that installs directly onto a physical server. With direct access to and control of underlying resources, VMware ESXi partitions hardware to consolidate applications and cut costs.
N/A
Pricing
AWS Elastic Beanstalk
AWS Lambda
VMware ESXi
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
There are many services like AWS Elastic beanstalk, but there are none with the maturity in the platform or the cost-effectiveness of AWS Elastic Beanstalk. Also, AWS Elastic Beanstalk is the oldest among them, so there are more people with AWS experience than the other …
The AWS platform provides a great deal of configurability that is abstracted and provided very well through AWS Elastic Beanstalk. This is the main reason for choosing Elastic Beanstalk over competing services. Another reason for selecting AWS Beanstalk was vendor …
Honestly, I haven't tried any other alternative products. As already mentioned, I am already heavily invested in AWS, so EBS was a natural choice for me. In other reviews, I have found, AWS is better than its competitors. There are more flavors, and options in AWS, better …
AWS Lambda is much easier to use than the near alternatives. It is so straightforward and lightweight it is my primary service for handling small transactions or triggers. The other services require more setup time and are more complex to use. AWS Lambda takes your code snippet …
AWS is great product and a close match our expectations. It is close to Azure in function but more feature rich with API and support documents. From my experience, it is cheaper compared with our competitors and provides better interface. Overall our dev engineers prefer AWS …
Each service has its purpose. With EC2 you can provision servers for customers and internal projects. With EBs you can optimize what you need in performance with what you can afford. With AWS Lambda you can integrate several of these tools to work together or acomplish …
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.
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.
If you're looking for the industry standard in server virtualization, I would recommend ESXi. After decades of expertise in the field, VMware continues to provide a strong product, production-ready, with an easy-to-learn interface that allows for quick management along with less costly upfront onboarding and training. Grab the free personal-use license and install in your homelab to start!
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.
Resource management. The automatic load balancing works very well to ensure no host is taxed disproportionately compared to the others.
Templates and cloning. It is very easy to set up a template and spin up new servers based on a specific setup. This makes server management very streamlined.
VM management. The vSphere interface is very easy to use and navigate. Everything is responsive and it works when you need it to. The options are also robust while also being arranged in a straightforward manner.
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.
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.
VMware ESXi can improve on the UI that is installed on the bare metal machine. The menus can be hard to navigate when looking for simple configuration items.
VMware ESXi can improve on the stability of their overall hypervisor. There have been a few times we had to reinstall due to corruption of VMware ESXi.
I would like to see VMware ESXi do better at adding more standard free features in their consumer version of VMware ESXi. For example, having the ability to back up virtual machines is good practice and something that would be very nice if offered in their free version.
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.
It is critical to our business, what started out as a way to do certain functions, it has now become core to ensuring our product is available to our customers and reducing our costs to operate and reduce our recovery time and provisioning servers. Their support is great and the costs to renew is reasonable.
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
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.
The interface is fairly intuitive for most things, and the areas that are a little less obvious usually have fantastic documentation in the online knowledgebase. In 3-4 years of managing our ESXi hosts, I think that I have only opened 4-5 support cases for things that I could not figure out myself or find answers to on the website.
Without the need to patch the servers with bug fixes and enhancements we whave not experienced any downtime with VMware issues. Even the bug fixes and updates do not cause of downtime as we just migrate the servers to the opposite node and update the one and then move servers back. Very simple and painless.
We do not notice any difference between a physical and virtual server running the same workload. In fact we can scale quicker with the virtual server than we can with the physical.
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.
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.
I can't say enough good about VMware's support team. To an individual they take ownership of the case, provide thorough answers, and follow up regularly. On one occasion, a problem we experienced with NSX Endpoint was escalated to development for a permanent resolution after a workaround was found. In my experience, most companies would have tried to find a way to close a case like that instead of taking it all the way. Most importantly, when production is down and every second counts, they VMware teams understand that urgency and treat your issue as if it were the only one they had to deal with. You can't ask for better.
- 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.
Jsut read and follow anything your storage provider may require to allow the integration of VMware with storage operations, outside of that VMware jsut works.
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.
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
As long as you're using Nutanix AOS on Nutanix hardware and are paying their software support fees, AOS is a valid competitor to VMware and can save money due to not needing a license and having their server management system built into the base host management system. If you aren't using Nutanix hardware, however, VMWare is in most cases the best way to go. I cannot comment on HyperV, but most IT people I know either use it because they have to (most) or they like it better (not many).
it has been fair and easy to understand. I know VMware is looking at wanting to change from CPU to core pricing so we will see what that looks like when it happens.
We started out with a two-server cluster and adding a third or fourth is very straightforward and simple with no issues. You just need to be aware of the size of your Vcenter Server to handle the workload, but still the resources needed is very minimal
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.
VMWare ESXi licensing is affordable for our business - and the licensing model is simplistic. Not like that of Microsoft with having to keep track of server licenses and CAL licenses for users.
VMWare ESXi also has hardware-monitoring built-in, so that further saves us money from having to be spent with another vendor.
As much as I hate the saying "a single pane of glass" does fit for this product. You can manage your servers, monitor hardware status, create and export backup snapshots, manage virtual NICs, connect to various storage devices. We're very happy with this product.
