heng4fun

I like the AGPL. The intent of AGPL is to encourage openness and collaboration, not to restrict or burden software developers. Many great projects choose this AGPL.

I had been keeping an eye on this project before, and upon checking it out recently, I've noticed many minor improvements. It's not just that one operator now supports multiple engines, but the feature experiences of several engines have also gradually become more well-rounded.

The performance impact of running databases on Kubernetes is not significant, as major cloud providers also use Kubernetes to run databases at scale.

KubeBlocks' ability to manage multiple database clusters is indeed an interesting feature.

Aha? Developers don't really love managing databases. It'd be ideal if they could just provide the type of database access I need, without having to deal with managing migrations, scaling, and all that other messy stuff.

One Operator that can manage multiple types of databases, complete with comprehensive operations management features. How is this achieved?

Most Operators can only manage one type of database, or at most, several CRDs.