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.2 out of 10
N/A
Dropbox is a cloud storage solution, equipped with features that help users to save time, improve productivity, and collaborate with others. Users can edit PDFs, share videos, sign documents, and collaborate with stakeholders without leaving Dropbox.
$9.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.
Ultimately, Dropbox just works better when working crossplatform between Windows, Mac, Andoid, ios. It's snappier compared to Google Drive and is overall a more pleasant experience. The lack of integration with the rest of Google's suite is a small sacrifice. Image preview is also snappier and more pleasant to use compared to drive. Though any large batches that need review should be relegated to a better image gallery hosting platform like pic-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.
Dropbox's real-time collaboration features, including simultaneous editing and commenting, have revolutionized the way our teams work together.
On multiple occasions, we've accidentally overwritten important documents or needed to retrieve deleted files. With Dropbox, we can easily revert to previous versions or recover deleted files, preventing data loss and minimizing disruptions.
Dropbox excels in making file sharing a breeze. With just a few clicks, we can generate shareable links or invite colleagues to shared folders.
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.
Change the name of the root folder, the "()" can cause problems sometimes with some tools trying to find paths inside of the root folder.
The upload queue becomes slow trying to upload files that have more than ~500mb of file size, even if I have 1 Gbit of speed, Dropbox gets stuck uploading single files with that rule.
Sometimes we can't move a shared folder from root location.
LAN sync seems not to be working in my experience.
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.
[Its] functionality and usability are very good, however[,] on every computer that I have ever installed the app on, Dropbox assumes I want it to update the files every time I start the system up. That's not always true, but the app assumes it is. I can switch that function off, but I would rather that function default to "Off" and then I can decide to turn it on as needed.
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.
Our experience with support has been limited which is a good thing. We haven't experienced any major issues with the service and most of our service interactions have been useability questions which we were able to find answers for within their knowledge base. For the few times we have reached out to support, the responses were on point, quick, and our issue was resolved in one interaction. I appreciate not being routed to a chatbot or offshored support.
- 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.
Dropbox gives more visual control over the success of uploading. WeTransfer uploads and then sends a link to the recipient. If something goes wrong during the upload, there doesn't appear to be a way to begin again from the dropping point. With Dropbox, I can watch as it uploads. If I lose a connection, it will continue uploading where it left off when I get a new connection. This is vital in transferring large files. If WeTransfer offers that, I was never able to figure it out.
