3 ms·
> The problem [...] isn't being surreptitiously billed a large amount, it is cost of a critical service changing dramatically without warning. Sorry, but this
by dozzie 9y ago
> The problem [...] isn't being surreptitiously billed a large amount, it is cost of a critical service changing dramatically without warning.
Sorry, but this is the risk of using somebody else's service -- especially
Google's -- as a critical component of a business. It may be marvellous for
developers not to bother with infrastructure for their own service, but this
strategy likes to come back and bite in the ass.
- radiowave 9y agoYou always have to use someone else's service - even if it's just the electricty supply. But different services come with different risks, and you have to try to gauge them.
- derefr 9y agoNo, this is the risk of using somebody else's service without getting your rates locked in with a contract. You know, a Service Level Agreement? Those things companies used to sign with their hosting providers, before all this IaaS stuff made developers feel like they could "start using now, talk to legal later"?