3 ms·

Thanks for reading, my post is primarily on telco, I have written how this can help telco applications and use cases, let me know if you wanted something specif

• bradknowles 3y ago
  See, now that's actually a lot more interesting to me. I work at AWS, but I didn't know that Kubernetes was heavily used in the telco business. Several years ago, I was part of a team that helped AT&T refactor their software they were running with Chef on top of OpenStack, and we were able to cut their codebase to a third of the size it started at, simply by removing duplication of modules and eliminating modules that weren't used. It took our team six months to do that, but we put in place CI/CD procedures that made sure everything still ran and passed all the tests, before we handed over the next batch of code updates. So, I'm guessing the telco business has moved away from OpenStack and to Kubernetes? IMO, helping people get the broader perspective of how something like this fits into their industry as a whole, or at least a major sector of the industry -- that's the kind of thing that I find to be much more interesting.
  • ram_rattle 3y ago
    yes, telecom network consists of two critical component, one is radio access network and other is core network, the core is already cloud native i.e the 3gpp specification itself is written for microservice architecture while the radio access network software's run on k8s but they are still big monoliths, I would say already 40% of 5G is running on k8s, few like dish even runs on vmware on aws.