Amazon Elastic Block Store (EBS) from AWS is designed for application workloads that benefit from fine tuning for performance, cost and capacity. Typical use cases include Big Data analytics engines (like the Hadoop/HDFS ecosystem and Amazon EMR clusters), relational and NoSQL databases (like Microsoft SQL Server and MySQL or Cassandra and MongoDB), stream and log processing applications (like Kafka and Splunk), and data warehousing applications (like Vertica and Teradata).
N/A
AWS Elastic Beanstalk
Score 9.0 out of 10
N/A
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
Pricing
Amazon Elastic Block Store (EBS)
AWS Elastic Beanstalk
Editions & Modules
No answers on this topic
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Offerings
Pricing Offerings
Amazon Elastic Block Store (EBS)
AWS Elastic Beanstalk
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Elastic Block Store (EBS)
AWS Elastic Beanstalk
Considered Both Products
Amazon Elastic Block Store (EBS)
Verified User
Employee
Chose Amazon Elastic Block Store (EBS)
Amazon Elastic Block Store (EBS) is a better option than Microsoft Azure Disk Storage for customers that require more volume-type options and cost-effective data archiving.
It provides the optimized storage performance and cost for your workload and these options really work with SSD-backed storage and it improves the database performance. Keeping backups of your EC2 resources, including EBS volumes is a little bit tricky and its takes some more time and increase through put is also a tiring job to do.
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.
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.
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.
Amazon EBS is a great tool and fairly easy to use as long as you are familiar with the Amazon Web Service ecosystem. It allows a great way for you to move storage around easily and allows you to quickly provision storage as needed based on the business requirement. For us, it's easy to move between our EC2 images that had been linked with EBS storage between these Amazon accounts.
It is a great tool to manage your applications. You just need to write the codes, and after that with one click, your app will be online and accessible from the internet. That is a huge help for people who do not know about infrastructure or do not want to spend money on maintaining infrastructure.
The support for Amazon Elastic Block Store is great as long as you can articulate your needs. Like most tools, there may be some back and forth before you find a support person that is knowledgable in the tool and can provide you with necessary insights.
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.
So far I have only used Amazon Elastic Block Store (EBS) and Azure but comparatively [I] prefer AWS elastic Block store as its having more advantages than Azure and I found it quite satisfactory and it helped a lot for information storage. We are not looking for any other hosting provider at this time.
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.
When your application needs high IOPS storage, this is a great solution that will keep your business functioning.
Without Amazon Elastic Block Store you could try spreading your data across several standard drives, but that introduces complexity and still has IOPS limits.
