Databases#
Several NeMo microservices use the PostgreSQL databases to store data such as entity metadata, custom fields, file locations, and file references.
By default, the NeMo Helm charts use the Bitnami PostgreSQL chart as a dependency with simplified authentication to enable quick installation. This may not be flexible enough for production use, and a full PostgreSQL instance is launched for each microservice using this method.
NeMo Evaluator uses Milvus for vector database storage.
NeMo Microservices that Require Database Setup#
The following table identifies the NeMo microservices that require database setup. For production, instead of deploying with the default database, set up your own external database.
Database |
Microservice |
Description |
|---|---|---|
PostgreSQL |
NeMo Data Store |
Stores repositories and Git large file storage (LFS) entries. |
NeMo Entity Store |
Stores platform-wide entities such as namespaces, models, and datasets. |
|
NeMo Customizer |
Stores configurations for model customizations. |
|
NeMo Evaluator |
Stores model evaluations. |
|
Milvus |
NeMo Evaluator |
Saves high-dimensional vector embeddings for Retriever Pipelines and RAG Pipelines. |
Configuration Guides#
Create an external PostgreSQL database for production use.