Contributor

Why it makes perfect sense for Dropbox to leave AWS

opinion
Apr 12, 20164 mins

On March 14, Dropbox announced it was 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.

Oleg Dulin is a Big Data software engineer and consultant in the New York City area.

In 1997 Oleg co-founded Clarkson University Linux Users Group. This group was influential in bringing awareness of open-source to Clarkson, and later morphed into what now is a dedicated lab and curriculum called Clarkson Open Source Institute. While at Clarkson, Oleg advocated on behalf of open-source and Linux and community and helped with construction of Clarkson’s first open-source high-performance computing cluster called “The North Country.”

While at IBM T. J. Watson Research Center in 1999-2000 Oleg co-authored a paper on federated information systems that was presented at Engineering of Federated Information Systems (EFIS) conference in 2000. This R&D project involved building a proof-of-concept federated IS that integrated structured (SQL) and unstructured (multi-media) data under a single set of API and user interfaces.

From 2001 to 2003 Oleg worked as a data integration consultant at a major investment bank in NYC on a web portal for private banking. This project involved aggregation of secure financial data from multiple legacy databases and presenting it in a customizable web portal.

In 2004, while working at a startup called ConfigureCode, Oleg contributed to two patent applications involving construction and semantic validation of mixed-schema XML documents. This technology was utilized in a Data Capture and Tracking System for Human Resources data integration.

From 2005 to 2011 Oleg worked at a Wall St. company (see Oleg’s LinkedIn Profile for more details) where he was instrumental in improving data quality, reducing trading errors, implementing analytics and reporting within the context of an equities order management system. The system was a 24/7 high performance computing platform that processed billions of dollars worth of trade executions daily.

From fall of 2011 to end of 2016, Oleg worked at Liquid Analytics as Cloud Platform Architect, where he was a thought leader in the implemention of a cloud-based PaaS for mobile Business Intelligence.

Presently, Oleg works at ADP Innovation Lab as Chief Architect.

The opinions expressed in this blog are those of Oleg Dulin and do not necessarily represent those of IDG Communications, Inc., its parent, subsidiary or affiliated companies.

More from this author