Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (31)

The future is bright Mar 30, 2025 Software Engineering is here to stay Mar 3, 2024 On luck and gumption Oct 8, 2023 Book review: Clojure for the Brave and True Oct 2, 2022 Why don’t they tell you that in the instructions? Aug 31, 2022 Monolithic repository vs a monolith Aug 23, 2022 Scripting languages are tools for tying APIs together, not building complex systems Jun 8, 2022 Good developers can pick up new programming languages Jun 3, 2022 Java is no longer relevant May 29, 2022 Automation and coding tools for pet projects on the Apple hardware May 28, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Best practices for building a microservice architecture Apr 25, 2022 Tools of the craft Dec 18, 2021 What programming language to use for a brand new project? Feb 18, 2020 Which AWS messaging and queuing service to use? Jan 25, 2019 The religion of JavaScript Nov 26, 2018 Let’s talk cloud neutrality Sep 17, 2018 TypeScript starts where JavaScript leaves off Aug 2, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Amazon Alexa is eating the retailers alive Jun 22, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 OAuth 2.0: the protocol at the center of the universe Jan 1, 2016 What Every College Computer Science Freshman Should Know Aug 14, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 The longer the chain of responsibility the less likely there is anyone in the hierarchy who can actually accept it Jun 7, 2015 Big Data is not all about Hadoop May 30, 2015 Exploration of the Software Engineering as a Profession Apr 8, 2015 Thanking MIT Scratch Sep 14, 2013 Have computers become too complicated for teaching ? Jan 1, 2013 Scripting News: After X years programming Jun 5, 2012

Why it makes perfect sense for Dropbox to leave AWS

May 7, 2016

This article was originally published on my Cloud Power blog at Computerworld on April 12th, 2016.

On March 14th, 2016 Dropbox publicly announced that they are moving out of the Amazon cloud. It makes perfect sense for Dropbox but should not be an excuse for a reluctant IT department not to proceed with their cloud implementation plans. Here are some of the reasons why it is the right move for Dropbox but unwise for a corporate IT department.

Dropbox is in the business of cloud services


Dropbox is far from being the dominant player in the cloud storage. Google Drive, One Drive and Box offer competing alternatives that are not difficult to migrate to. Likewise, AWS faces tough pricing pressures from their competitors.

Dropbox earns their profit margins on the difference between their technology investments and earnings from the services. So does AWS. Both compete with other cloud services providers in their respective areas. Each of them needs to keep lowering the costs while also earning money.

Dropbox is a technology company


Unlike a corporate IT department, Dropbox is a technology-first company for whom IT is a profit center. With heavy investment in technology they are able to innovate and invent new approaches to distributed storage.

In his Wired article on Dropbox exodus from AWS, Cade Metz says:
Over the last two-and-a-half years, Dropbox built its own vast computer network and shifted its service onto a new breed of machines designed by its own engineers, all orchestrated by a software system built by its own programmers with a brand new programming language.

Only a handful of corporate IT departments with tech-company budgets can afford to invent their own hardware, network storage protocols, and programming languages. The vast majority of corporate IT departments rely on old guard vendors whose main source of income is in milking of the installed base.

Dropbox can attract and retain top talent


In his article called “How To Find the Next Generation of IT Leaders” IDG contributor Esteban Herrera writes:
Corporate IT is not sexy. In my generation, IT was an attractive career. We knew the Internet would shake things up, and corporations had big appetites—and big dollars—for people who could implement and manage corporate systems. Today, few young people get excited about a career in corporate IT. For one thing, they know it is a job they could lose to outsourcing—they might as well work for the service provider and have more job security. The truth is most won’t even do that. Young people with technology skills want to be with Google, Uber, Amazon or the next Facebook. Not only do these employers offer fun, millennial-friendly work environments, they also offer jobs that are quite lucrative, and their employees can enjoy knowing they really are changing the world.

Corporate IT was never sexy or attractive to top talent. Four year computer science programs never prepared graduates for a career in the maintenance of business computer systems – nor do computer science students want to.

Dropbox is routinely listed in the top tier of the most desirable companies to work for. Dropbox employees consider Dropbox the best company to work for and write articles on what it is like to work there. Try as they might, corporate IT departments simply do not have the budget and the culture to compete for the top talent.

Final thoughts


Outsourcing is a simple manifestation of the capitalist division of labor, in which one company hires another to do something that they can’t do on their own. Cloud computing commoditizes routine and yet expensive tasks such as infrastructure and data center maintenance. Dropbox’s decision to roll their own cloud infrastructure does not mean that AWS is inadequate for more traditional corporate IT. IT departments should only roll their own technologies if they have the budget and the talent to do it better than a cloud provider.