Skip to content

Update README icon #261

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

Open
zhangh43 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README icon #261

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
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,29 +38,29 @@ Explore [EloqDoc](https://www.eloqdata.com/product/eloqdoc) for more details, or

## Key Features

### ⚙️ MongoDB API Compatibility
### MongoDB API Compatibility

Seamlessly integrates with MongoDB clients, drivers, and tools, enabling you to use existing MongoDB workflows with a distributed backend.

### 🗃️ Tiered Storage Architecture
### Tiered Storage Architecture

EloqDoc seamlessly manages hot and cold data across **memory, local NVMe cache, and object storage**. Since NVMe storage is ephemeral and lost when a node crashes, EloqDoc uses it strictly as a cache for object storage. This design ensures that all data remains safe and durable in cross-AZ object storage while still benefiting from NVMe-level performance for frequently accessed data.

### 🌐 Truely Distributed Database
### Truely Distributed Database
Copy link

@coderabbitai coderabbitai bot Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix spelling error: "Truely" → "Truly".

Line 49 contains a spelling error in the section heading.

-### Truely Distributed Database
+### Truly Distributed Database
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Truely Distributed Database
### Truly Distributed Database
🤖 Prompt for AI Agents 
In README.md around line 49, the section heading contains a misspelling "Truely
Distributed Database"; change "Truely" to "Truly" so the heading reads "Truly
Distributed Database" and save the file.


Supports **multiple writers** and **fast distributed transactions**, ensuring high concurrency and fault tolerance across a cluster without sharding complexity.

### 🔄 Elastic Scalability
### Elastic Scalability

- Scales compute and memory **100x faster** than traditional databases by avoiding data movement on disk.
- Scales storage independently, so CPU resources remain constant when data volume grows but traffic stays the same.
- Scales redo logs independently to optimize write throughput.

### 🔥 High-Performance Transactions
### High-Performance Transactions

Delivers **ACID transaction support** with especially fast distributed transactions, making it suitable for mission-critical applications.

### 🔒 Simplified Distributed Design
### Simplified Distributed Design

Operates as a distributed database without requiring a sharding coordinator (e.g., `mongos`), reducing operational complexity and overhead.

Expand Down