Invisible IT Infrastructure (Coffee as a Service)

2:45 · Watch on YouTube ↗

Transcript 418 words · about 3 min to read

Auto-generated captions from YouTube, not hand-corrected, so names and technical terms may be imperfect. The video is authoritative.

hice keeps town sir from the CTO advisor calm with a quick coffee chat coffees outside the shot so sorry for you caffeine heads we're going to talk a little bit about the invisible infrastructure just like we're having the invisible coffee today there's the awful lot of work that goes into the invisible infrastructure I think one of the things that I'm realizing is that there's a perception that the invisible infrastructure means that there is simplicity ie I can go and have a instant cup of coffee the

instant cup of coffee is really easy to deploy drinking it however is a very different experience than taking your time you know there's a person in the virtualization community Cody Cody that spends an awful lot of time brewing his own coffee you can go to them and just get overwhelmed by tips on how to prepare coffee and make the coffee the infrastructure and then there's the consumption of the coffee well if I met a technology event and there's Cody I'll just say you know what Cody

give me a cup of coffee and he goes behind the scenes does all the infrastructure things brings that coffee to the forefront and I drink the coffee it was the work that it took for him to rolls the beans to select the beans to roast the beans to grind the beans to do all of the infrastructure for cold brewing they're all the researching and work of two cold brew a coffee and then deliver that to me it's all invisible so while there's a concept that the

infrastructure should be invisible which it should be the those things you shouldn't burden the user with I shouldn't be burden on what it takes to provision a server to patch a server to maintain a server and networking and load balancers and etc however that doesn't mean that those things are simple and that the preparation and creation and deployment of those things are relatively without effort on the back end of the design it just means from a consumption perspective it's easy for me to consume and I

don't see the preparation involved in making that happen so that's it quick coffee chat talk to you guys next CTL advisor you can follow me on the web the CTO advisor comm subscribe to the podcast the CTO visor icon for / podcast or catch P in iTunes talk to you guys on Twitter at CTO visor