Did you ever ask yourself if cgroups (containers, pods, whathaveyou) can impact the @golang runtime? I did and here's what I learned... (thread) 👇#Docker #Kubernetes #Linux So ~2y ago, while working with a lot of customers moving into containers and #Kubernetes, I naturally hit the (now well-known) Java/JVM cgroups issues (all you need to know -> lightbend.com/blog/cpu-consi… and ).

Service meshes provide a lot of value, especially around encryption and observability. I question, though, whether circuit breaking/timeouts/retries should be externalized (deferred) to the network. (Thread) These app-specific (business logic) concerns are impossible to generalize at scale/ in large distributed systems, ie the ones where you typically consider a service mesh.

I see a lot of people having problems to understand how the Kubernetes platform works at the fundamental level, e.g. resiliency and behaviour. If you start thinking about Kubernetes as a fully event-driven system, there's answers to so many "Why"'s Think of the API server as an immutable (replicated) log (queue) and stream of events. Events are facts that can be causally related ("happened-before") or not related at all (then we say they happened "concurrently"). etcd is an implementation detail.