AUTO: Sync ScalarDB docs in English to docs site repo (#1797)

Co-authored-by: josh-wong <joshua.wong@scalar-labs.com>

Author: github-actions[bot]

docs/roadmap.mdx

@@ -18,31 +18,29 @@ If you have a feature request or want to prioritize feature development, please
 
 :::
 
-### CY2025 Q3
+### CY2025 Q4
 
 #### Support for additional databases
 
 - **TiDB**
     - Users will be able to use TiDB as an underlying database through ScalarDB Core and ScalarDB Cluster.
 - **AlloyDB**
     - Users will be able to use AlloyDB as an underlying database through ScalarDB Core and ScalarDB Cluster.
-- **Spanner**
-    - Users will be able to use Spanner as an underlying database through ScalarDB Core and ScalarDB Cluster.
+- **Azure Blob Storage**
+    - Users will be able to use Azure Blob Storage as an underlying database through ScalarDB Cluster.
+- **Amazon S3**
+    - Users will be able to use Amazon S3 as an underlying database through ScalarDB Cluster.
+- **Google Cloud Storage**
+    - Users will be able to use Google Cloud Storage as an underlying database through ScalarDB Cluster and ScalarDB Analytics.
 
 #### New features
 
 - **Decoupled metadata management**
     - Users will be able to start using ScalarDB Cluster without migrating or changing the schemas of existing applications by managing the transaction metadata of ScalarDB in a separate location.
 - **Role-based access control (RBAC)**
     - Users will be able to define roles and assign permissions to those roles so that users can manage access control in a more flexible way.
-- **Views**
-    - Users will be able to define views so that they can manage multiple different databases in an easier and simplified way.
 - **Addition of SQL operations for aggregation**
     - Users will be able to issue aggregation operations in ScalarDB SQL.
-- **Universal catalog**
-    - Users will be able to manage metadata, including schemas and semantic information, for operational and analytical databases across separate business domains in a unified manner.
-- **Universal authentication and authorization**
-    - Users will be able to be given access to ScalarDB Cluster and ScalarDB Analytics by using a unified authentication and authorization method.
 
 #### Improvements
 
@@ -70,14 +68,20 @@ If you have a feature request or want to prioritize feature development, please
 - **LLM-friendly rule files for ScalarDB**
     - Users will be able to ask questions and tasks to LLMs by using the LLM-friendly rule files so that LLMs can work for them with a better understanding of ScalarDB. The rule files will be designed to provide LLMs with the necessary context and instructions to effectively interact with ScalarDB, making it easier for users to leverage AI capabilities in their applications.
 
-### CY2025 Q4
+### CY2026 Q1
 
 #### New features
 
 - **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, users cannot define a multi-column index. The new secondary index will be created at the ScalarDB layer so that users can create more flexible indexes, like a multi-column index.
-- **Two-layered query engines**
-    - Users will be able to use two-layered query engines to better federate analytical queries across domains. The first-layer query engine is responsible for federating analytical queries across various domains, while the second-layer query engine federates analytical queries within a specific domain across its corresponding databases.
+- **Views**
+    - Users will be able to define views so that they can manage multiple different databases in an easier and simplified way.
+- **Authentication with OIDC**
+    - Users will be able to authenticate to ScalarDB Cluster and ScalarDB Analytics by using OpenID Connect (OIDC).
+- **Universal catalog**
+    - Users will be able to manage metadata, including schemas and semantic information, for operational and analytical databases across separate business domains in a unified manner.
+- **Universal authentication and authorization**
+    - Users will be able to be given access to ScalarDB Cluster and ScalarDB Analytics by using a unified authentication and authorization method.
 
 #### Usability
 
@@ -86,38 +90,79 @@ If you have a feature request or want to prioritize feature development, please
 - **Elimination of out-of-memory errors due to large scans**
     - Users will be able to issue large scans without experiencing out-of-memory errors.
 
-#### Support for additional databases (object storage)
-
-- **Azure Blob Storage**
-    - Users will be able to use Azure Blob Storage as an underlying database through ScalarDB Cluster.
-- **Amazon S3**
-    - Users will be able to use Amazon S3 as an underlying database through ScalarDB Cluster.
-- **Google Cloud Storage**
-    - Users will be able to use Google Cloud Storage as an underlying database through ScalarDB Cluster and ScalarDB Analytics.
-
 #### Performance
 
+- **Batch operations in SQL**
+    - Users will be able to issue operations in a batch in ScalarDB SQL so that they can improve performance when executing multiple operations by reducing the number of roundtrips between applications and ScalarDB Cluster.
+- **Piggyback operations in SQL**
+    - Users will be able to piggyback BEGIN and COMMIT operations on data operations in ScalarDB SQL so that they can improve performance when executing multiple operations within a transaction by reducing the number of roundtrips between applications and ScalarDB Cluster.
 - **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.
 
 #### Cloud support
 
-- **Container offering in Azure Marketplace for ScalarDB Cluster**
-    - Users will be able to deploy ScalarDB Cluster by using the Azure container offering, which enables users to use a pay-as-you-go subscription model.
-- **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.
+- **Azure support for ScalarDB Cluster**
+    - Users will be able to deploy ScalarDB Cluster by using the Azure marketplace offering, which enables users to use a pay-as-you-go subscription model.
 
-### CY2026
+### CY2026 Q2
+
+#### New features
 
 - **Audit logging**
     - Users will be able to view and manage the access logs of ScalarDB Cluster and Analytics, mainly for auditing purposes.
+- **Two-layered query engines**
+    - Users will be able to use two-layered query engines to better federate analytical queries across domains. The first-layer query engine is responsible for federating analytical queries across various domains, while the second-layer query engine federates analytical queries within a specific domain across its corresponding databases.
+- **LangGraph4j integration**
+    - Users will be able to use LangGraph4j to build AI applications that can interact with ScalarDB.
+
+#### Performance
+
+- **Predicate pushdown**
+    - Users will be able to benefit from predicate pushdown in ScalarDB Analytics so that filtering operations are pushed down to the underlying databases to reduce data transfer and improve query performance.
+
+#### Cloud support
+
+- **Azure support for ScalarDB Analytics**
+    - Users will be able to deploy ScalarDB Analytics by using the Azure marketplace offering, which enables users to use a pay-as-you-go subscription model.
+
+#### Integration
+
+- **Kong integration**
+    - Users will be able to integrate ScalarDB Cluster with Kong Ingress Controller so that they can manage and secure access to ScalarDB Cluster more easily.
+
+### CY2026 Q3
+
+#### New features
+
 - **Stored procedures**
     - Users will be able to define stored procedures so that they can execute a set of operations with a complex logic inside ScalarDB Cluster.
 - **Triggers**
     - Users will be able to define triggers so that they can automatically execute a set of operations when a specific event occurs in ScalarDB Cluster.
+- **Queue interface**
+    - Users will be able to use ScalarDB as a message queue so that they can build event-driven architectures more easily.
+
+#### Performance
+
+- **Adaptive caching**
+    - Users will be able to benefit from adaptive caching in ScalarDB Analytics so that frequently accessed data is cached automatically to improve query performance.
+
+#### Cloud support
+
+- **Google Cloud Platform (GCP) support for ScalarDB Analytics**
+    - Users will be able to deploy ScalarDB Analytics by using the GCP marketplace offering, which enables users to use a pay-as-you-go subscription model.
+
+#### Integration
+
+- **Red Hat Ecosystem Catalog integration**
+    - Users will be able to deploy ScalarDB Cluster from Red Hat Ecosystem Catalog, which enables users to use ScalarDB Cluster as Red Hat-certified third-party products and services.
+
+### CY2026 Q4
+
+#### New features
+
 - **User-defined functions (UDFs)**
     - Users will be able to define functions so that they can use functions in SQLs to express complex logic in a simpler way.
-- **Addition of SQL operations for sorting**
-    - Users will be able to issue arbitrary sorting (ORDER BY) operations in ScalarDB SQL for multiple or non-JDBC databases. (Currently, ScalarDB can issue sorting operations using clustering keys or arbitrary sorting operations for single JDBC databases.)
-- **Addition of more data types**
-    - Users will be able to use complex data types, such as JSON.
+- **GraphDB support**
+    - Users will be able to use GraphDBs as underlying databases through ScalarDB Cluster.
+
+### CY2027