周正德13642
unread,May 22, 2021, 1:36:20 AM5/22/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to orchestrator-mysql, shlomi.noach, sjmudd, tim, 章明星17329, 吴国才55013
Hi guys,
We are the team from sangfor. First of all, orchestrator is indeed a very amazing MySQL high availability and replication management tool. It supports a variety of failure recovery methods, and it can be simple and convenient for topology management. Not only has a very good ui, but also provides http and cli interfaces for fine-grained control. More importantly, it also solves its own high availability problem, which is indeed a very great project.
However, in many of our customers, different applications often use different types of databases, and databases other than mysql still face the same problems. So we decided to refactor orchestrator to support more types of database high availability and replication management, such as openguass. We used the adaptor design pattern, and adopted the interface method to realize some common functions. For this reason, we made relatively big changes. Our goal is that in the future, in one orchestrator cluster, multiple different types of database clusters can be managed at the same time, such as mysql, postgres, openguass, etc.
Thank you very much for the ideas and inspiration that orchestrator has brought us. We will also open source the refactored high-availability and replication management tools. Could you give us some suggestions or can we give back to the orchestrator community?
Look forward to hearing from you soon.
Regards