Skip to content

Cloud Costs

Cloud cost models are sometimes weird, and billing sometimes is not quite transparent. The cost model can also change at will.

The Medium story reported by Home Automation is an extreme example, and contains a non-trivial amount of naiveté on their side, but underlines the importance of being spread through more than one cloud provider and having an exit strategy. Which is kind of a dud, if you are using more than simple IaaS – if you tie yourself to a database-as-a-service offer, you can’t really have an exit strategy at all.


TL;DR: Firebase accidentally wasn’t billing some traffic, and fixed that (the billing). They did not communicate the change, they did not update their status panels to report the increased traffic, and they did not measure the billing impact of their change to find extreme cases before the change and contact them.

The customer, Home Automation, has close to zero clue to using TLS correctly, was using connection inefficiently and kind of maximised overhead, ran into the worst case scenario for the change, got fucked. They would want out, but also had zero strategy for that, because DBaaS fuckup.

In the cloud you don’t need operations. Until you do.

Published inContainers and Kubernetes


  1. Rince

    Well – most of the time you Need to be Aware what the cloud Service is doing for you – and what happens if they Change anything on their side.
    So you do not Need only Exit strategies but the knowledge _where_ it will affect your Business if they Change anything on their side. And you have to be Aware of These possibilities.
    Of course, you can ignore this. but then you get fucked because you have no way to tell the cloud Provider to Change back. or to make another Change in your favour. You are dependent on _his_ model, Business and payment.

  2. Well, as an old-school admin I’m used to put an reverse-proxy (Apache etc.) in front of each and every tomcat/container/whatnot-microservice-thingy out there to filter requests, perform redirects and stuff and of course to terminate the TLS-connection.

  3. BrianR

    “if you tie yourself to a database-as-a-service offer, you can’t really have an exit strategy at all.”

    A database-as-a-service built on open source technology would enable exiting.

Leave a Reply

Your email address will not be published. Required fields are marked *