docs(README): update badges and improve formatting for clarity
- Replaced the Cartographer badge with the npm package version badge to align with the current project focus. - Added commented-out placeholder for the removed Cartographer badge for future reference. - Enhanced text formatting in `README.md` to improve readability and alignment consistency. - Updated scaling strategy section to separate lines for readability. - Clarified deployment details for GitHub Pages and linked workflows.
This commit is contained in:
parent
32c1ca891f
commit
23e84e43ce
1 changed files with 9 additions and 4 deletions
13
README.md
13
README.md
|
|
@ -6,7 +6,9 @@
|
|||
[](https://nodejs.org/)
|
||||
[](https://www.typescriptlang.org/)
|
||||
[](CONTRIBUTING.md)
|
||||
[](https://github.com/sodal-project/cartographer)
|
||||
[](https://www.npmjs.com/package/@soulcraft/brainy)
|
||||
|
||||
[//]: # ([](https://github.com/sodal-project/cartographer))
|
||||
|
||||
**A powerful graph & vector data platform for AI applications across any environment**
|
||||
|
||||
|
|
@ -1026,7 +1028,8 @@ The repository includes a comprehensive demo that showcases Brainy's main featur
|
|||
interactive demo on
|
||||
GitHub Pages
|
||||
- Or run it locally with `npm run demo` (see [demo instructions](README.demo.md) for details)
|
||||
- To deploy your own version to GitHub Pages, use the GitHub Actions workflow in `.github/workflows/deploy-demo.yml`,
|
||||
- To deploy your own version to GitHub Pages, use the GitHub Actions workflow in
|
||||
`.github/workflows/deploy-demo.yml`,
|
||||
which automatically deploys when pushing to the main branch or can be manually triggered
|
||||
- To use a custom domain (like www.soulcraft.com):
|
||||
1. A CNAME file is already included in the demo directory
|
||||
|
|
@ -1221,13 +1224,15 @@ await db.shutDown()
|
|||
|
||||
## 📈 Scaling Strategy
|
||||
|
||||
Brainy is designed to handle datasets of various sizes, from small collections to large-scale deployments. For terabyte-scale data that can't fit entirely in memory, we provide several approaches:
|
||||
Brainy is designed to handle datasets of various sizes, from small collections to large-scale deployments. For
|
||||
terabyte-scale data that can't fit entirely in memory, we provide several approaches:
|
||||
|
||||
- **Disk-Based HNSW**: Modified implementations using intelligent caching and partial loading
|
||||
- **Distributed HNSW**: Sharding and partitioning across multiple machines
|
||||
- **Hybrid Solutions**: Combining quantization techniques with multi-tier architectures
|
||||
|
||||
For detailed information on how to scale Brainy for large datasets, see our comprehensive [Scaling Strategy](scalingStrategy.md) document.
|
||||
For detailed information on how to scale Brainy for large datasets, see our
|
||||
comprehensive [Scaling Strategy](scalingStrategy.md) document.
|
||||
|
||||
## Requirements
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue