Re:ApeRAG: Production-ready GraphRAG with multi-modal indexi...
by popalchemist on Thursday September 11, 2025 @06:29PM
(#45216763)
This is a very typical, and pretty bare-bones stack. Almost any production grade webapp above a minimal threshold of complexity will have database, cache, and search.
Re:ApeRAG: Production-ready GraphRAG with multi-modal indexi...
by CuriouslyC on Thursday September 11, 2025 @06:22PM
(#45216710)
Postgres isn't a replacement for elastic. You CAN get full text search working in postgres, and for very basic use cases it's good enough, but it's vastly inferior to elastic in terms of features and performance.
Re:ApeRAG: Production-ready GraphRAG with multi-modal indexi...
by freakynit on Sunday September 14, 2025 @06:07AM
(#45238757)
Exactly. These "extensions".. they are good, but, far from being replacements for dedicated products, the quality of which customers have come to expect.
Re:ApeRAG: Production-ready GraphRAG with multi-modal indexi...
by CharlesW on Thursday September 11, 2025 @05:40PM
(#45216386)
HelixDB is a database. ApeRAG is an application that uses multiple databases (but that not particular one). Hypothetically, you could fork ApeRAG and modify it to use that database.
Re:ApeRAG: Production-ready GraphRAG with multi-modal indexi...
by cipherself on Thursday September 11, 2025 @06:23PM
(#45216725)
In the list of features, it mentions:
> vision-based search for comprehensive document understanding
but it's not clear to me what this means, is it just vector embeddings for each image in every document via a CLIP-like model?
In addition, I'd be curious what's the rationale behind using the plethora of databases, given the docs on running it in production spins them all up, I assume they're all required, for instance I'd be curious on the trade-offs between using postgres with something like pg_search (for bm25 support, which vanilla postgres FTS doesn't have) vs using both postgres and ElasticSearch.
The docs are also very minimal, I'd have loved to see at least 1 example of usage.
geez
sorry but, how much SHIT is it going to take to make AI good?
https://github.com/HelixDB/helix-db
> vision-based search for comprehensive document understanding
but it's not clear to me what this means, is it just vector embeddings for each image in every document via a CLIP-like model?
In addition, I'd be curious what's the rationale behind using the plethora of databases, given the docs on running it in production spins them all up, I assume they're all required, for instance I'd be curious on the trade-offs between using postgres with something like pg_search (for bm25 support, which vanilla postgres FTS doesn't have) vs using both postgres and ElasticSearch.
The docs are also very minimal, I'd have loved to see at least 1 example of usage.
> bash ./02-install-database.sh # Deploys PostgreSQL, Redis, Qdrant, Elasticsearch
Is this built on top of all databases ? I am just trying to understand.