> ApeRAG requires PostgreSQL, Redis, Qdrant, and Elasticsearch. You have two options: > bash ./02-install-database.sh # Deploys PostgreSQL, Redis, Qdrant, Elasticsearch Is this built on top of all databases ? I am just trying to understand.
ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment
11–15 of 15 posts
Re: ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment
#12> bash ./02-install-database.sh # Deploys PostgreSQL, Redis, Qdrant, Elasticsearch geez sorry but, how much SHIT is it going to take to make AI good?
Re: ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment
#13> ApeRAG requires PostgreSQL, Redis, Qdrant, and Elasticsearch. You have two options: > bash ./02-install-database.sh # Deploys PostgreSQL, Redis, Qdrant, Elasticsearch Is this built on top of all databases ? I am just trying to understand.
Yes, ApeRAG uses all these databases.
Re: ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment
#14Earlier quoted context omitted.
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.
This is just one of a million other wrappers around AI that will be forgotten in a few months.
Re: ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment
#15Earlier quoted context omitted.
What’s funny is Postgres alone can handle this entire workload decently well.
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.