Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Irony: Dropbox saved 75 million by moving away from cloud hosting - Nextcloud

Irony: Dropbox saved 75 million by moving away from cloud hosting


Dropbox, in its S1-statement last Friday, showed it reduced its operating costs by nearly 75 million over the next two years by moving storage away from Amazon onto its own infrastructure. Cost savings are only one part of why moving away from cloud storage can be beneficial, but it is a significant driver.

Self-hosting, Hybrid and Public Cloud

Dropbox is described by Geekwire as:

once the quintessential cloud success story, a startup that built a massive user base and brand presence thanks to its use of Amazon Web Services

When this company finds out that a well understood compute and storage problem is more cheaply solved on their own infrastructure rather than a public cloud, any business leader should wonder about their own needs and what is cost-effective. Indeed, unpredictable, quick moving and irregular needs offer an area where public clouds have large benefits. But the bigger an organization grows, the deeper its understanding of what drives its compute needs and the more cost-effective it becomes to host those in-house. If needed, perhaps, with a dash of public cloud overflow for those busy days or special needs. Only, of course, for non-sensitive data!

You can read many more details on the epic story of Dropbox moving to its own data centers in this story on wired.com – including details like a move from Golang to Rust due to the formers’ memory footprint, and more.

Security increases costs

Typically, security costs are vague and hard to calculate. But the recent Meltdown and Spectre bugs in commonly used CPU’s, which have allowed hackers to breach the security of containers since before cloud was even a thing, had a profound and direct impact: decreased performance of public clouds. The Register reported on several customers noticing sizable performance impact from the patches, resulting in higher costs. If you pay per minute or hour, a 20% performance hit means tasks run longer and cost more.

Of course, that is entirely on top of those hard-to-calculate costs of data breaches, soon to be increased by new regulations like the GDPR.

The final picture

The picture this paints is one that shows the much heralded cost benefits of cloud computing to be not as certain as some thought. While some workloads, especially those that are very variable and unpredictable, most certainly benefit from being executed on the infrastructure of big players like Google, Amazon and Microsoft, others don’t provide much of a cost benefit and, more importantly, create security and compliance risks. A thorough analysis of costs, benefits and risks is crucial to determine what the right choice is.

EDIT: just today, the 27th, some more irony reached the news… The Inquirer reports that Apple stores iCloud data on Google and Amazon’s cloud infrastructure!

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.