3 years ago

Category: Software, Kubernetes, Docker, Infrastructure, Architecture, github

On the cloud native journey, there are both general lessons and best practices that apply to nearly all companies as well as industry-specific challenges. Cloud native journeys aren’t one-size-fits-all; the best way to handle storage, networking, security and even back-ups depends on the specifics of both the industry and the individual company.

Here’s what he had to say about best practices both for other telecoms as well as everyone making the move to cloud native.

Today, we develop all our products using cloud native principles, such as being infrastructure agnostic and using open APIs, and we continuously re-architect our portfolio to be Cloud Native Network Functions.

Kubernetes and cloud native technologies were developed primarily for IT workloads and environments, and we found their networking capabilities fall short of telecom needs.