Skip to content

AUTO: Docs repo sync - ScalarDB #976

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2025
Merged

AUTO: Docs repo sync - ScalarDB #976

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions versioned_docs/version-3.13/roadmap.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ If you have a feature request or want to prioritize feature development, please

#### Security

- **Fine-grained access control**
- Users will be able to authorize accesses to the underlying databases in a finer-grained way. In addition to the current simple authorization where ScalarDB checks if users are authorized to issue particular operations, ScalarDB will check if users can access particular records.
- **Attributed-based access control (ABAC)**
- Users will be able to authorize accesses to the underlying databases in a finer-grained way. In addition to the current simple authorization where ScalarDB checks if a user is authorized to issue particular operations to a table, ScalarDB will check if a user can access particular records based on the attributes of the user and the records.

#### Usability

Expand Down Expand Up @@ -68,7 +68,7 @@ If you have a feature request or want to prioritize feature development, please
#### Performance

- **Removal of WAL-interpreted views in ScalarDB Analytics**
- Users will be able to read committed data by using ScalarDB Core instead of WAL-interpreted views.
- Users will be able to read committed data by using ScalarDB Core instead of WAL-interpreted views, which will increase query performance.

### CY2025 Q3

Expand All @@ -86,7 +86,7 @@ If you have a feature request or want to prioritize feature development, please
#### Scalability and availability

- **Semi-synchronous replication**
- Users will be able to provide ScalarDB-based applications in a disaster-recoverable manner. For example, assume you provide a primary service in Tokyo and a standby service in Osaka. In case of catastrophic failure in Tokyo, you can switch the primary service to Osaka so that you can continue to provide the service without data loss and extended downtime.
- Users will be able to replicate the data of ScalarDB-based applications in a disaster-recoverable manner. For example, assume you provide a primary service in Tokyo and a standby service in Osaka. In case of catastrophic failure in Tokyo, you can switch the primary service to Osaka so that you can continue to provide the service without data loss and extended downtime.

### CY2025 Q4

Expand Down