It looks like this project is for more than just MySQL. Should the title get updated? Also, the `Quick Start` link in the readme goes to a 404.
Sorry about that. Fixed now.
An open-source MySQL alternative for running database on Kubernetes
11–20 of 61 posts
Re: An open-source MySQL alternative for running database on Kubernetes
#12It looks like a fully managed database service alternative.
MySQL, PostgreSQL, Redis, MongoDB... all the popular db engines.
Re: An open-source MySQL alternative for running database on Kubernetes
#13If this is supposed to be used in production as open source, then I am a little surprised that it's under AGPL 3.0, especially given there's no mention of commercial version.
Unless you were using a modified version without making your changes available, why would this be a problem?
AGPL is viral, requiring you open source of all source involved in serving network clients, not only this AGPL software itself.
It's meant to close the serve-over-the-network loophole of the GPL.
Re: An open-source MySQL alternative for running database on Kubernetes
#14So now instead of debugging database performance issues you also have to debug the third party database orchestration middleware and the Kubernetes cluster workloads.
Re: An open-source MySQL alternative for running database on Kubernetes
#15So now instead of debugging database performance issues you also have to debug the third party database orchestration middleware and the Kubernetes cluster workloads.
That is the reason why you need KubeBlocks, it takes over the complexity.
Re: An open-source MySQL alternative for running database on Kubernetes
#16It seems that this can not only manage databases but also support Kafka and Pulsar.
Re: An open-source MySQL alternative for running database on Kubernetes
#17This seems interesting but this passage from the readme is a red flag to me: >You do not have to learn database tuning. KubeBlocks can leverage storage and computing resources to achieve optimal database performance. No one has ever delivered on this pipe dream.
I think the key word here is "you". You just get it running, hack your spaghetti and when it becomes a problem you're already assigned on another project so someone else will have to sort it out.
And that guy is usually me.
Just remember when you leave a pool of shit behind, one of the victims might be making a hiring decision about you at some point in the future.
Re: An open-source MySQL alternative for running database on Kubernetes
#18I 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.
Re: An open-source MySQL alternative for running database on Kubernetes
#19This seems interesting but this passage from the readme is a red flag to me: >You do not have to learn database tuning. KubeBlocks can leverage storage and computing resources to achieve optimal database performance. No one has ever delivered on this pipe dream.
So... throw money on compute instead of just adding an index..?
Seems Kubeblocks provids some parameters templates based on their knowledge on databases. To some extent, it will improve performance. Of course, I don't think users will be totally freed from `database tuning`, which is too complex a topic.
Re: An open-source MySQL alternative for running database on Kubernetes
#20This seems interesting but this passage from the readme is a red flag to me: >You do not have to learn database tuning. KubeBlocks can leverage storage and computing resources to achieve optimal database performance. No one has ever delivered on this pipe dream.
So... throw money on compute instead of just adding an index..?
I’m offended that you don’t take even 10 minutes to understand why this will not work.
People say they don't need sysadmins and stuff like this is the result.
Vertical scalability limits are very soon met and can be difficult to fix post-fact.