-----Original message----- > The important takeaways here are two: 1. ensuring service stability > and 2. ensuring that long term business continuity isn't compromised > (e.g. vendor lock-in). Once these requirements are fulfilled, it's > great to get an inside view of what the NCC's plans are.
During the previous discussion thread on this mailinglist I mentioned the risk for loss of skill/proficiency, in the newly published Labs article I haven't seen any statements about that? This could be a direct impact on business continuity. The original article mentioned the engineers already have worries about maintaining the current infrastructure, instead of helping them to the next level, the NCC is planning to take away all their playground and hand it over to some cloud provider who now will do that job. Over time as more services could be migrated to the cloud, the required skill-set for self-hosted services will fade, engineers might even get bored and leave to other employers where they can build and maintain their own infra again. In the end, the competence needed for the NCC to take everything back in-house when said cloud provider cannot fulfill anymore will be a PITA. Once more, I would like to point to a very interesting and eye-opening presentation by Bert Hubert about this very topic: https://www.youtube.com/watch?v=PQccNdwm8Tw (transcript: https://berthub.eu/articles/posts/how-tech-loses-out/ )
