Before understanding use cases, it's useful to know what Frabit is. This page lists some popular Frabit use cases.
Database Change Automation
Similar to how GitLab/GitHub streamlines the code delivery, Frabit streamlines the database change deployment from the non-prod environment all the way to the prod environment. Bytebase also integrates with VCS to enable GitOps workflow. You can manage database change scripts in VCS and Bytebase will start a new deployment process whenever observing the new change scripts.
You can also integrate Frabit's CLI bb into your existing CI/CD workflow.
Data Access Control
Organizations want to limit database access and enforce approval flow to conform compliance and avoid data leaks. Bytebase provides a suite of features to support this:
- Data Query Approval Flow
- Data Export Approval Flow
- Data Masking
- Data Access Control
- Watermark
- Audit Log
Database Developer Portal
As the engineering team grows, there will form a platform team or a dedicated DBA team to manage the database infrastructure and support developers to interact with their application databases. Bytebase provides a centralized portal for Developers/DBAs/Community Engineers to collaborate on database-related tasks such as reviewing database changes, querying data, backing up and restoring databases and etc.
Deploy database cluster
As data grows, databases and tables maybe partitioned into smaller chucks. Meanwhile, you still want to apply the same database change to all partitions since they share the same schema. It's painful and error-prone to make sure a database change is consistently applied to each partition. Bytebase has Database Group and can change databases from database groups.
Schema Enforcement and Engineering Excellence
Data quality and system robustness are largely determined by the database schema. And being able to enforce standards consistently is the key to a high-quality schema. Bytebase can enforce schema rules including naming convention, anti-SQL pattern detections and etc. You can also configure each individual rule for prod and non-prod environments respectively.