AWS Elastic Beanstalk vs. Carbonite by OpenText

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

More than enough for small companies with several on-prem servers. In 2021, it wouldn't be wise to pit all important data to a single backup service. Carbonite Server is solid, but it's not 100% reliable so I'd definitely recommend having multiple backup services either on the cloud in conjunction with other backup services so the user has multiple safety nets in case of disaster and failed granular restorations.

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

• Simple administrative web interface - It's easy to provision users, look at data usage stats, disable users, and update policies to control what folders users are allowed to backup, and what options they can access
• Easy client installation - Installing and updating clients was very simple. The client would notify the user when a new update was approved by the site admins, and they typically went very smoothly.
• Good performance - Backups went fairly fast, and were generally invisible to the user, other than the icon updating on files to indicate whether the current version of a file was backed up or not.

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

• While overall file restoration is easy to do, obtaining earlier versions is not as user friendly as it could be. You need to enter a date and click search to bring up the latest versions as of the date entered. That’s fine, but what is missing is the ability to see all versions of an individual file. If I am looking for a past file version I want to be able to view the file history as a subset of that file (in other words I should be able to click a + sign and expand to see past versions of the file). Otherwise I am just guessing which dates the file was changed in the past. Sometimes that’s OK, but Mozy needs to build in this enhanced, but necessary feature.
• A couple of years ago, for non enterprise users, Mozy made radical storage and pricing changes forcing myself and many users off their system, as the price for the same storage was going up significantly. So be careful when using Mozy as past experience has shown they are willing to make major changes regardless of the negative impact on their users.

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

Carbonite Server Backup does not integrate or support any reporting; it is not good at it. We required monthly and quarterly reports for audit. If we fail in that we get fined or we have to pay a certain amount of money to customer. It does not support cloud instances and we are using N2WS for the cloud instances. This is an additional burden for customers.

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

Out of all the vendor we deal with they are one of the best when it comes to customers service. Reliable,you can reach them by telephone easily, Great overall can not say anything to the contrary. Usibility is excellent. I recommend them highly whether you need a simple backup ofr more complex for servers etc.

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

I usually find what I need to know by looking in the Carbonite knowledge base online. We haven't had any major problems, usually we just need clarification on a point or more details about a feature so we look it up. We haven't had to call in for help in quite awhile.

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 had appliance and we just needed to setup the Director Console which was straight forward and easy.

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

Netbak is a great product but we also had a secondary issue of having to backup several PC's on site and at remote locations. Carbonite helped with both and gave us one central admin console to be able to check the progress of all our backups, where netbak would have required us to setup a tunnel or use the internet to move data back to our main office.

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

• We have a safety net that we didn't have before.
• Key players are now backed up through an automated system that was easy to silently install.
• The resources used impacted our exchange server negatively and slowed email until it was disabled.

Incentivized