AUTO: Sync ScalarDB docs in English to docs site repo

Author: josh-wong

docs/overview.mdx

@@ -58,6 +58,12 @@ Modern architectures, like the microservice architecture, encourage a system to
 
 ScalarDB simplifies managing such diverse databases with a correctness guarantee (or, in other words, ACID with strict serializability), enabling you to focus on application development without worrying about guaranteeing consistency between databases.
 
+### Simplifying data management in a data mesh
+
+Enterprises have been investing their time in building [data meshes](https://martinfowler.com/articles/data-mesh-principles.html) to streamline and scale data utilization. However, constructing a data mesh is not necessarily easy. For example, there are many technical issues in how to manage decentralized data.
+
+ScalarDB simplifies the management of decentralized databases in a data mesh, for example, by providing a unified API for all the databases in a data mesh to align with the data-as-a-product principle easily.
+
 ### Reducing database migration hurdles
 
 Applications tend to be locked into using a certain database because of the specific capabilities that the database provides. Such database lock-in discourages upgrading or changing the database because doing so often requires rewriting the application.

docs/roadmap.mdx

@@ -17,25 +17,23 @@ If you have a feature request or want to prioritize feature development, please
 
 :::
 
-### CY2024 Q3 
+### CY2024 Q4
 
 #### New capabilities
 
-- **Data virtualization for non-transactional storage operations**
-    - Users will be able to run non-transactional storage operations on diverse data sources through ScalarDB. This enhancement will virtually unify various data stores, like relational databases and NoSQL databases, without regard to whether the data sources are managed by ScalarDB transactions.
 - **Data virtualization for analytics**
     - Users will be able to run read-only OLAP SQL queries on diverse data sources through ScalarDB Analytics. ScalarDB Analytics currently supports only ScalarDB-managed data stores, so this enhancement will virtually unify various data stores, like relational databases and NoSQL databases, and files in cloud object stores, like Amazon S3, without regard to whether the data sources are managed by ScalarDB transactions.
+- **Vector store abstraction**
+    - Users will be able to store and search embeddings (vectors) in and from vector stores through a new vector store interface in ScalarDB. With this feature, users can simplify the process of realizing retrieval-augmented generation (RAG) with large language models (LLMs) by reading data from databases through the existing ScalarDB interface, creating embeddings from the data, and storing and searching the embeddings to and from a vector store through the new interface.
 
 #### Security
-
-- **Transparent data encryption**
-    - Users will be able to specify what columns to be encrypted. ScalarDB will encrypt records in a transparent manner where records will be encrypted before writing them to disk and the records will be decrypted before sending them back to users.
+- **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.
 
 #### Usability
 
 - **Addition of time-related data types**
     - Users will be able to use time-related data types, which will make their existing applications easier to migrate.
-
 - **Removal of extra-write strategy**
     - Users will no longer be able to use the extra-write strategy to make transactions serializable. Although ScalarDB currently provides two strategies, extra-read and extra-write strategies, to make transactions serializable, the extra-write strategy has several limitations. For example, users can't issue write and scan operations in the same transaction. Therefore, the strategy will be removed so that users don't need to worry about such limitations when creating applications.
 
@@ -45,6 +43,8 @@ If you have a feature request or want to prioritize feature development, please
     - Users will experience faster execution for simple transactions that write to a single partition. ScalarDB will omit the prepare-record and commit-state phases without sacrificing correctness if a transaction updates only one partition by exploiting the single-partition linearizable operations of the underlying databases.
 - **Reduction of storage space needed for managing ScalarDB metadata**
     - Users will likely use less storage space to run ScalarDB. ScalarDB will remove the before image of committed transactions after they are committed. However, whether or not those committed transactions will impact actual storage space depends on the underlying databases.
+- **Removal of coordinator writes for read-only transactions**
+    - Users will experience faster execution for read-only transactions by removing coordinator writes for those transactions.
 
 #### Cloud support
 
@@ -53,11 +53,12 @@ If you have a feature request or want to prioritize feature development, please
 - **Google Cloud Platform (GCP) support**
     - Users will be able to deploy ScalarDB Cluster in Google Kubernetes Engine (GKE) in GCP.
 
-### CY2024 Q4
+### CY2025 Q1
 
-#### 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.
+#### New capabilities
+
+- **Native secondary index**
+    - Users will be able to define flexible secondary indexes. The existing secondary index is limited because it is implemented based on the common capabilities of the supported databases' secondary indexes. Therefore, for example, you cannot define a multi-column index. The new secondary index will be created at the ScalarDB layer so that you can create more flexible indexes, like a multi-column index.
 
 #### Usability
 
@@ -71,24 +72,7 @@ If you have a feature request or want to prioritize feature development, please
 - **Addition of more data types**  
     - Users will be able to use more data types so that their existing applications will be easier to migrate.
 
-#### Performance
-
-- **Removal of coordinator writes for read-only transactions**
-    - Users will experience faster execution for read-only transactions by removing coordinator writes for those transactions.
-
-#### Cloud support
-
-- **Red Hat OpenShift support**
-    - Users will be able to use Red Hat–certified Helm Charts for ScalarDB Cluster in OpenShift environments.
-- **Container offering in Google Cloud Marketplace**
-    - Users will be able to deploy ScalarDB Cluster by using the Google Cloud container offering, which enables users to use a pay-as-you-go subscription model.
-
-### CY2025 Q1 -
-
-#### New capabilities
-
-- **Native secondary index**
-    - Users will be able to define flexible secondary indexes. The existing secondary index is capable of the intersection of what the underlying databases' secondary indexes are capable of; thus, it is very limited. The new, native secondary index creates indexes at the ScalarDB layer so that it is more flexible. For example, the native secondary index can define multi-column indexes.
+### CY2025 Q2 -
 
 #### Usability
 
@@ -99,3 +83,10 @@ If you have a feature request or want to prioritize feature development, please
 
 - **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.
+
+#### Cloud support
+
+- **Red Hat OpenShift support**
+    - Users will be able to use Red Hat–certified Helm Charts for ScalarDB Cluster in OpenShift environments.
+- **Container offering in Google Cloud Marketplace**
+    - Users will be able to deploy ScalarDB Cluster by using the Google Cloud container offering, which enables users to use a pay-as-you-go subscription model.