But this post isn't about that. It's about our increased reliance on external tools, workflows and providers. While being more agile we seem to sacrifice a lot of our knowledge, without even thinking about the business risks.
EaaP - Ecosystem as a Problem
If your cloud provider shuts down, your business dies
WE AND OUR AFFILIATES OR LICENSORS WILL NOT BE LIABLE TO YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES (INCLUDING DAMAGES FOR LOSS OF PROFITS, GOODWILL, USE, OR DATA), EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. FURTHER, NEITHER WE NOR ANY OF OUR AFFILIATES OR LICENSORS WILL BE RESPONSIBLE FOR ANY COMPENSATION, REIMBURSEMENT, OR DAMAGES ARISING IN CONNECTION WITH: (A) YOUR INABILITY TO USE THE SERVICES, INCLUDING AS A RESULT OF ANY [...] (II) OUR DISCONTINUATION OF ANY OR ALL OF THE SERVICE OFFERINGSOf course this will never happen, just keep believing it...
If the team building your deployment workflow decides to quit
Yes, you have made your developers life easier, they just commit code to the repository, click one button and then magic happens. Congratulations, you have just replaced your former operations team with the ecosystem team. You can proudly use the term DevOps. The end result is mostly the same, if they quit at once or your upper management decides that they are doing nothing, because everything works and no shiny features are shown, and as such are just a money sink, you have at least a month to replace them and get them up to speed. 90% of your developers won't have any idea what's going on behind the scenes. I once had a situation where a developer asked what's a mountpoint, and it wasn't a junior dev... So good luck.