AWS Elastic Beanstalk vs. DreamHost

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.

Incentivized

Dreamhost was previously a great web host with reliable service and top-notch features, but I can no longer recommend them. If you're looking for web hosting on a Linux platform (such as running PHP or platforms like Wordpress, Jooma, or Drupal), with simple pricing services, then this is the great service for you. One big downside is lack of phone customer support. This is especially frustrating because of their many issues the last few weeks, which aren't easily resolved or addressed by their team.

Incentivized

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

Incentivized

• Customer service is industry-best. We've never had a problem that wasn't solved by them almost immediately.
• Their dashboard is extremely easy to use and doesn't cause any confusion at all.
• Their website speeds are good but not great. In an age when speed is important, they are good enough, especially for the price.
• They have a great backup feature.

Incentivized

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

Incentivized

• They could have better deploy solutions for not so experienced users
• More integration with external services to automate some tasks
• Better ways to track hosting performance
• The user management could be easier to understand

Incentivized

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.

Incentivized

We have every intention of staying with Dreamhost, but we are a tad concerned with the company's recent involvement in high profile litigation and controversial topics. While we don't take a position one way or another on what type of content they should host, one concern we have is that repeated attacks on their infrastructure have caused significant downtime during business hours for us, and that's something we'll have to take into consideration going forward.

Incentivized

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

Incentivized

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.

Incentivized

Whether we're calling in on the phone, live chatting or emailing, we get immediate high-quality, native English-speaking support. This cannot be overstated when it comes to hosting, because support tickets are usually time sensitive and high stress. I've always had great experiences with the limited times we've needed to use DreamHost support. We've dealt with support for many other providers and no one comes close to DreamHost.

Incentivized

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

Incentivized

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.

Incentivized

We've tried a few other WordPress-specific hosts, as well as other shared hosting providers (Rackspace, WPEngine, and others). We have found that DreamHost gives the best balance of cost, performance, and features, for our needs. All vendors have their own pitfalls and shortcomings, and DreamHost isn't without its own, but it works for us.

Incentivized

• till now we had not Calculated ROI as the project is still evolving and we had to keep on changing the environment implementation
• it meets our purpose of quick deployment as compared to on-premises deployment
• till now we look good as we also controlled our expenses which increased suddenly in the middle of deployment activity

Incentivized

• The service can really be a positive value with its very solid performance and lack of downtime issues found with other services.
• For those with limited hosting or web development knowledge, the service can be a challenge to fully utilize. Sometimes this may mean additional training.
• The service also provides a number of expansion opportunities for growing with greater functionalities.

Incentivized