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
HPE 3PAR StoreServ
Score 8.5 out of 10
N/A
HPE 3PAR StoreServ is a flash storage option, from Hewlett-Packard Enterprise.
N/A
Pricing
AWS Elastic Beanstalk
HPE 3PAR StoreServ
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
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.
HPE 3PAR StoreServ is a great storage device for both file and block-level storage needs. You can use it in place of SAN devices required by database servers. It provides an amazing compaction ratio and, hence, reduces overall storage footprint and cost. This is, however, slightly costly if your environment doesn't really see high transactions most of the time.
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.
We are using HP 3PAR storeServ 8200 for both our file level and block level storage.
I really love the amazing compaction ratio provided by HP 3PAR. Some of our disks have compaction ratio above 25:1, which is super amazing. You can definitely look for around 75% reduction of storage footprints.
It has a great user friendly web console "SSMC"(StoreServ Management Console). This is an additional bonus and can be used by even non-storage people like DBA and Network to take a look at storage performance.
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 system requires a physical or virtual system to manage upgrades and patches and for call home features. Most other systems have this integrated into the array. Just another piece of infrastructure to manage.
There are some system jobs that come pre-scheduled in the initial setup, but there is at least 1 job that should be added to this by default. When you delete storage, you also need to run a job to compact the CPG (a group where the luns all reside) to reclaim the previously used storage as free. This should be done by default at least monthly in the background.
There are 2 different GUI front ends that can still be used. The older version (3 PAR management console) is being phased out (has been for 3 years).
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 very satisfied with 3PAR performance and especially the IOPS (Input Output Per Second) is pretty amazing. It is easy to configure and doesn't require much knowledge of storage for Tier 1 support team.
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.
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.
With their phone home technology, we usually have a replacement part on its way by the time we wake up in the morning, or if the event occurs overnight. We have had great support when we had questions or events that required a call.
- 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.
We still use NetApp storage enclosures at each plant for our routine file shares (CIFS) but I would love to swap them out for the HPE 3PARs as we use for our ERP app data. The 3PARS are simply faster and much better at near-instant replication. But even more importantly we can get the reporting that we need from the 3PAR within a few minutes, even custom reports. 3PARs are much easier to manage than NetApps in general and I think that the only place that they compete is in compaction.
