3 ms·
If you have the money for it, as in, a developer may be able to create infrastructures at whim, but does he have all the necessary money to pay for all the bill
by sysadmdev 6y ago
If you have the money for it, as in, a developer may be able to create infrastructures at whim, but does he have all the necessary money to pay for all the bills related to that cloud? (Paying for processing, storage, networking, etc)
We already know of a few cases where a bug in code got a few thousands of dollars of damage.
Imagine that multiplied by the number of objects created on an array that generates clouds in real-time in a developer's code.
It's a pretty pricy bug.
- sysadmdev 6y agoThere's also the issue with control and monitoring, giving a lot more control to the Cloud Provider and total surveillance of operations to third parties. I can see a future where only 1 cloud remains and all our tools and resources are on the Cloud Provider's Infrastructure and we cannot control or even self-host our own tools and data and everything we do and host is being monitored. If someone does not agree with what we store or host, it may be rejected and even banned/deleted WITH our consent (because we accepted the EULA) but without our authorization. We would not own anything we create or send to the cloud. We would all become Cloud Developers, Cloud Web Developers, Cloud Engineer, Cloud SRE in our resumees. This should be more open and not be driven by Vendor Lock-in.