Skip to content

Commit 3e1d556

Browse files
committed
docs: update dbeaver
1 parent 7438748 commit 3e1d556

File tree

2 files changed

+25
-11
lines changed

2 files changed

+25
-11
lines changed

content/blog/bytebase-vs-cloudbeaver.md

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,13 @@ Bytebase focuses on team collaboration, offering tailored features like access c
3131
| [Installation](#installation) | Jave-based, require JVM | Deploy Go-binary with no external dependency |
3232
| [Supported databases](#supported-databases) | Free for 13, Paid for 80+ | 20+ |
3333
| [Query](#query) |||
34-
| [Change](#change) | Direct | Review workflow |
35-
| [Access control](#access-control) | ✅ basic | ✅ Free for basic version / Paid for advanced version |
34+
| [Change](#change) | ⚠️ Direct | ✅ Configurable direct or review workflow |
35+
| [Access control](#access-control) | ⚠️ Basic | ✅ Free for basic version / Paid for advanced version |
3636
| [Data masking](#data-masking) || ✅ Paid |
37-
| [Compare Schema](#compare) || ✅ 1:N |
37+
| [Compare Schema](#compare-schema) || ✅ 1:N |
3838
| [Audit log](#audit-log) |||
39+
| [API](#api) | ✅ GraphQL | ✅ gRPC + HTTP/REST |
40+
| [GitOps](#gitops) | ⚠️ No built-in solution ||
3941

4042
### Product position
4143

@@ -88,15 +90,15 @@ Bytebase focuses on team collaboration, offering tailored features like access c
8890
You may turn on **Query History** to track activities.
8991
![cb-change-query-history](/content/blog/bytebase-vs-cloudbeaver/cb-change-query-history.webp)
9092

91-
- **Bytebase**: Every change to the database should proceed through an issue. The issue will automatically bring you **SQL Review**, **Custom Approval Flow** and other related features.
93+
- **Bytebase**: Admin can configure whether to allow direct change or enforce the review process. When the review process is enforced, every change to the database will proceed through an issue. The issue will automatically bring you **SQL Review**, **Custom Approval Flow** and other related features.
9294
![bb-issue](/content/blog/bytebase-vs-cloudbeaver/bb-issue-waiting.webp)
9395

94-
Every change will be recorded in the **Change History**. Bytebase will also detect the schema changes made by other tools and mark them as **Schema Drift**.
95-
![bb-history](/content/blog/bytebase-vs-cloudbeaver/bb-history.webp)
96+
Every change will be recorded in the **Change History**. Bytebase will also detect the schema changes made by other tools and mark them as **Schema Drift**.
97+
![bb-history](/content/blog/bytebase-vs-cloudbeaver/bb-history.webp)
9698

97-
If you write a SQL script such `ALTER TABLE` in **SQL Editor**, you'll either create a new issue or switch to **Admin mode** (similar to SSH in the terminal).
98-
![bb-force-issue](/content/blog/bytebase-vs-cloudbeaver/bb-force-issue.webp)
99-
![bb-force-issue-preview](/content/blog/bytebase-vs-cloudbeaver/bb-force-issue-preview.webp)
99+
If you write a SQL script such `ALTER TABLE` in **SQL Editor**, you'll either create a new issue or switch to **Admin mode** (similar to SSH in the terminal).
100+
![bb-force-issue](/content/blog/bytebase-vs-cloudbeaver/bb-force-issue.webp)
101+
![bb-force-issue-preview](/content/blog/bytebase-vs-cloudbeaver/bb-force-issue-preview.webp)
100102

101103
On the other hand, the more common way to change the schema is to use **Schema Editor**.
102104

@@ -129,7 +131,7 @@ On the other hand, the more common way to change the schema is to use **Schema E
129131
Furthermore, `Admins`/`DBAs` can define semantic types for masking algorithms, such as email, phone, credit card, etc. As a result, the data will be masked according to the semantic type configured.
130132
![bb-masking-graph](/content/blog/bytebase-vs-cloudbeaver/bb-masking-graph.webp)
131133

132-
### Compare
134+
### Compare Schema
133135

134136
- **CloudBeaver**: Not available.
135137

@@ -146,6 +148,18 @@ On the other hand, the more common way to change the schema is to use **Schema E
146148
- **Bytebase**: **Audit Log** is available for the **Enterprise plan**. It records all the activities within Bytebase which can be filtered or exported.
147149
![bb-audit-log](/content/blog/bytebase-vs-cloudbeaver/bb-audit-log-dropdown.webp)
148150

151+
### API
152+
153+
- **CloudBeaver**: Support [GraphQL](https://github.com/dbeaver/cloudbeaver/wiki/Server-API-explorer), while the doc is pretty light.
154+
155+
- **Bytebase**: Support gRPC and HTTP/REST. Bytebase provides extensive [docs](/docs/api/overview/), [code samples](https://github.com/bytebase/api-example), and [tutorials](/tutorial/).
156+
157+
### GitOps
158+
159+
- **CloudBeaver**: In theory, you can build GitOps solution via the GraphQL API, but there is no mature solutions.
160+
161+
- **Bytebase**: [GitOps best practice](https://github.com/bytebase/api-example/tree/main/data-security) to configure every aspect of database security.
162+
149163
## Summary
150164

151165
This article compares Bytebase and CloudBeaver across various aspects, highlighting their unique strengths. CloudBeaver supports a wider range of databases, whereas Bytebase offers enhanced collaborative features for database management, including access control and change review capabilities. After all, in any use case, feel free to pick the one you're most comfortable with.

src/app/[locale]/sql-editor/page.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ import { BlogPost } from '@/types/blog-post';
77

88
export const metadata = getMetadata(SEO_DATA.SQL_EDITOR);
99

10-
const POSTS = ['top-dbeaver-alternative', 'top-open-source-sql-clients', 'stop-using-navicat'];
10+
const POSTS = ['bytebase-vs-cloudbeaver', 'bytebase-vs-dbeaver', 'stop-using-navicat'];
1111

1212
const SQLEditorPage = () => {
1313
const relatedPosts: BlogPost[] = [];

0 commit comments

Comments
 (0)