HN user

igmor

44 karma
Posts0
Comments25
View on HN
No posts found.

These components are very different in complexity and scope. Let's be real: a seasoned developer is mostly familiar with load balancers and ingress controllers, so this will be mostly about naming and context. I agree though once you learn about k8s it becomes less mysterious but that also means the author hasn't pushed it to the limits. Outages in the control plane could be pretty nasty and it is easy to have them by creating an illusion everything is kind of free in k8s.

The Sphere 2 years ago

Been there yesterday, can confirm what the author wrote about immersion. Cathedral and opera scenes are something I have never experienced before, fully blown away. The storyline is garbage.

It's weird because he calls it out in the comparison as a potential explanation for the gap in average booking per ride:

"This gap is likely also due to Uber’s heavier international presence (where they now generate 52% of their bookings). It would be interesting to see this data on a country-by-country basis (or, more importantly, a market-by-market one as well)."

yet still proceeds to draw this questionable conclusion: "Lyft has made impressive progress at increasing the value of rides on its platform and increasing the share of transactions it gets."

From documentation:

Traffic Director delivers a GCP-managed Pilot along with additional capabilities such as global load balancing and centralized health checking. However, note that Traffic Director cannot be configured using Istio APIs in this Beta release; you can use GCP APIs for configuration. Both Traffic Director and Pilot use open standard APIs (xDS v2) to communicate with service proxies.