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
Dropbox
Score 8.0 out of 10
N/A
Dropbox is a service for file syncing and sharing, or for cloud storage.
$11.99
per month
Pricing
AWS Elastic Beanstalk
Dropbox
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.
Well-Suited Scenarios: Large Design Files: Dropbox is well-suited for architects who work with large design files, such as blueprints, CAD files, and 3D models. Dropbox's large file sharing capabilities make it easy to share these files with team members and clients, while its version control features allow architects to track changes over time. Limited Customization: Dropbox may be less appropriate for me who require a high level of customization in my workflow or project management.
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.
At one point 2 gigs [were] deemed enough for the "Free" version of Dropbox and its competition. However as even the most simple picture from a phone gets larger, 2 gigs might no longer be enough. Might want to increase the free size to adjust for file size inflation.
Dropbox's app is very presumptive of updating itself every time you log on to a system that it's installed on. I know that's a feature you can turn off, but the assumption to turn that feature on by default is annoying.
Dropbox could use a phone app function that would initiate a download to a designated computer hard drive. It would eliminate having to see the file on your phone, go to your computer, turn it on and then download the file.
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.
Dropbox is a user-friendly, easy tool which requires little to no skill and they offer a free version with a good amount of storage available. There are other file sharing tools available however at a cost. Dropbox free version I have used for years and it serves every purpose I need.
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.
Dropbox is dead simple to us since right out of the box, it creates a folder on your PC and anything added to it gets synced to the cloud and any other device signed into that account. You can then dive deeper into permissions, version history, etc. Overall though, the minimalist approach is welcome since not everyone we work with is highly technical and that itself saves us time and money. Many of our colleagues already use Dropbox for their personal cloud so no training is required when using it at work other than going over our own company guidelines and best practices.
Dropbox is really useful, you can access any file from anywhere and you can upload and even edit files online, but, sometimes it can be slow. Downloading, uploading, and syncing is a bit slow, it can take several minutes. Furthermore, the search engine for large amounts of data can be slow too and it is not powerful.
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.
It has not been necessary to go to customer support lately, since everything works perfectly. However, I must add that at the beginning when I started using Dropbox, and I had any doubts about how it worked, customer support was always attentive and found the best solutions effectively.
- 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.
I needed to stay current in improving my daily operations. Dropbox was suggested to me by a former colleague two-years ago and I've been using it just fine ever since.
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.
Compared to Google Cloud Storage, the Dropbox app has proven to be more stable and dependable. In the meantime, Google has improved and is a great alternative. But now that we've decided to stick with Dropbox, we'll keep using it. In terms of ease of use, Dropbox appears to be the better option. It has all of the features that we require and more. It's easier to use for simple tasks, making it more convenient.
