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.
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!
Nextcloud Hub 9 te permite estar conectado. Descubre nuevas funciones de federación, automatización del flujo de trabajo, una gran revisión del diseño y mucho más en tu plataforma de colaboración de código abierto favorita.
Organisations, small and large, need a way to ensure the resiliency and digital sovereignty of their operations – an open-source, privacy-respecting alternative to Teams. And today, we present that solution - Nextcloud Talk.
In this article, we find out how open-source AI gets you your privacy back and explore examples of reliable AI models that you can use in your ecosystem.
On December 3rd, we invite you to the Nextcloud Enterprise Day Paris, Nextcloud's flagship event for professionals. The day will kick off with a keynote by our CEO and founder, Frank Karlitschek—a highlight where he will share our vision for the future of online collaboration, followed by a major announcement about Nextcloud Talk!
Guardamos algunas cookies para contar los visitantes y facilitar el uso del sitio. Esto no sale de nuestro servidor y no es para rastrearte personalmente. Consulta nuestra política de privacidad para obtener más información. Personalización
Las cookies estadísticas recopilan información de forma anónima y nos ayudan a comprender cómo utilizan nuestro sitio web nuestros visitantes. Utilizamos Matomo alojado en la nube.
Matomo
_pk_ses*: Cuenta la primera visita del usuario
_pk_id*: Ayuda a no contar dos veces las visitas.
mtm_cookie_consent: Recuerda que el usuario ha dado su consentimiento para almacenar y utilizar cookies.
_pk_ses*: 30 minutos
_pk_id*: 28 días
mtm_cookie_consent: 30 días