Hacker News Reader

So now instead of debugging database performance issues you also have to debug the third party database orchestration middleware and the Kubernetes cluster workloads.

View on HN

There is always an 'orchestration' middleware in some form, you just can't avoid it. The key is if the benefit it gives overcomes the complexity it introduces.

That is the reason why you need KubeBlocks, it takes over the complexity.

That is not how complexity works. You might lower the difficulty in the happy path, but when something goes wrong, there is additional complexity, and that means more places to debug and understand.

This is my primary objection to 3rd party kubernetes operators. I really don't care how hard something is to setup or learn to manage. I care how hard it is to recover, tune, and scale.

> when something goes wrong

Thank for correctly stating “when,” not “if”.

Abstractions are wonderful until they aren’t, at which point you’d better know how everything underneath them works.

I thought that the point was the solution architecture also guarantees increased complexity.

Reply on news.ycombinator.com