ADR 0051 - Evaluating vector databases as AppCat services
Author |
Simon Beck |
|---|---|
Owner |
Schedar |
Reviewers |
|
Date Created |
2026-01-14 |
Date Updated |
2026-01-14 |
Status |
draft |
Tags |
database,service |
|
Summary
Exisitng AppCat services already provide some vector capabilities. For any other use-cases the required databases should be provided as solutions. |
Context
More customers require vector databases for various AI related workloads.
To provide the best services possible some of the most popular open source solutions are evaluated in this ADR.
Solutions being evaluated:
-
OpenSearch/ElasticSearch
-
PostgreSQL with pgvector
-
Redis
-
Chroma
-
Qdrant
-
Milvus
OpenSearch/ElasticSearch
OpenSearch/ElasticSearch provides vector capabilities out of the box. Either one of these products are already on the roadmap for AppCat.
PostgreSQL with pgvector
StackGres and CNPG both already provide the pgvector extension.
For StackGres it needs to be installed via the extensions stanza.
CNPG pre-installs it in their default image.
So the vector capabilities of our PostgreSQL offering is already there.
Additional documentation to make users aware of this feature is recommended though.
Redis
Redis also provides vector capabilities out of the box. Redis provides documentation on how to use it: redis.io/docs/latest/develop/get-started/vector-database/#prepare-the-demo-dataset
Dedicated Vector databases
Criteria |
Chroma |
Qdrant |
Milvus |
Installation |
community helm chart, but very limited functionality, missing HA |
Official Helm chart available, enterprise operator |
Official chart and operator available |
Backup |
Export tool available, filesystem snapshots and filesystem snapshots |
||
Metrics |
|||
Maintenance/2nd-day operations |
Administration guides available that cover a lot of topics |
||
Update/Upgrade |
Migration guide available, recent rewrite in rust, rewrite doesn’t have authentication |
Automated via their operator |
|
License |
Apache License 2.0 |
Apache License 2.0 |
Apache License 2.0 |
Chroma
Chroma’s maturity doesn’t seem to be there, many things are not documented on the official page but rather on a community driven page. Only a rudimentary helm chart is available. The recent rewrite in rust dropped features that were previously available.
Decision
The AppCat portofolio already contains two existing services that provide vector capabilities. OpenSearch/ElasticSearch is on the roadmap. These services and products are very well understood and widely used. AppCat should provide documentation to make users aware of the vector capabilities of these services.
The dedicated vector databases might fit some use cases better, but of the three concrete requests we got, three different products were mentioned or requested. Given the initial effort to make a service AppCat managed, it’s not feasible to add these services just for 1-2 instances. In these cases the databases should be handled as a solution. If at one point the adoption and demand for a specific product increases, the need to provide it as a self-service AppCat service can be re-evaluated.