Lead Site Reliability Engineer at Anova. MSc in Computer Science by the University of Porto. Certified Kubernetes Administrator (CKA) and Certified Kubernetes Application Developer (CKAD) by the Cloud Native Computing Foundation (CNCF). Working daily to build high-performance, reliable and scalable systems. DevOps Porto meetup co-organizer and DevOpsDays Portugal co-organizer. A strong believer in culture and teamwork. Open source passionate, taekwondo amateur, and metal lover.
Network Service Mesh
A Runtime Domain, fundamentally a compute domain, is the environment where your workloads run. Normally, each Runtime Domain has only one Connectivity Domain. In practice, this means workload shave only one connectivity option and only workloads in that Runtime Domain can be part of that Connectivity Domain. There’s a strong coupling between Runtime Domains and Connectivity Domains.
Cloud-Native workloads are all about loose coupling and where a workload is running is unimportant. Workloads that, together, provide a certain service require connectivity and don’t care where other components live. Network Service Mesh (NSM) tackles this problem, by allowing your workload to work together, independent of where they’re running.