How we migrated onto K8s in less than 12 months

Re:How we migrated onto K8s in less than 12 months by ahoka on Friday August 09, 2024 @05:08AM (#41200106)

Oh, come on! Just make sure your architecture is sound. If you need to run an expensive data analysis cluster connected to massive streams of collected call information to see that you have loops on your architecture, then you have a bigger issue.

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by hylaride on Friday August 09, 2024 @09:37AM (#41201697)

I don't know if you're being sarcastic, which if you are: heh.

But to the point, if you're going to build a distributed system, you need tools to track problems across the distributed system that also works across teams. A poorly performing service could be caused by up/downstream components and doing that without some kind of tracing is hard even if your stack is linear.

The same is true for a giant monolithic app, but the sophisticated tools are just different.

[ Parent | on HN ]