A couple of years ago, we had an interesting idea. When a development team within an organization consists of around 10 members or fewer, controlling the risks associated with database changes might be achieved through trust and real-time communication. However, as the team grows, the responsibilities within the team become more specialized. Imagine a scenario where different branches of the business exist, each with its own set of developers, team leads, testers, testing leads, DBAs, and more. Relying solely on traditional communication methods becomes increasingly challenging when it comes to managing change risks.
Envision a platform where a change request goes through a sequence of checks: it's first reviewed by colleagues familiar with the business, then approved by the business lead, followed by scrutiny from the database lead, and finally assessed for security by the security lead. Does this approach effectively control the risk associated with that change when it's executed?In 2019, we embarked on building the first piece of this puzzle: ODC. Fast forward to today, after more than three years of development, ODC has evolved from a specialized developer tool designed for OceanBase (OB) into an enterprise-grade collaborative control platform, with plans to support multiple data sources.
And today, we are thrilled to announce that we are open-sourcing our project. You can find the entire four-year code history on GitHub (https://github.com/oceanbase/odc).
We're excited to hear your thoughts on this concept and whether you identify any potential challenges or opportunities that lie ahead. Your insights will play a crucial role in shaping the future of this project.
Looking forward to your feedback!