Skip to content
This repository was archived by the owner on Jun 8, 2026. It is now read-only.
This repository was archived by the owner on Jun 8, 2026. It is now read-only.

Feature Request: Stateless Deployment for Horizontal Scalability #382

Description

@moonward-capital

Feature Request: Stateless Deployment for Horizontal Scalability

Is your feature request related to a problem? Please describe.

Currently, the Verba container appears to operate in a stateful manner, which can pose limitations when scaling the application to handle a large number of concurrent requests. To effectively scale horizontally, it's necessary to run multiple instances of the Verba container. However, the existing architecture, which seems to store data within the container's local filesystem, prevents a stateless deployment model.

Describe the solution you'd like

To enable horizontal scalability, we propose the ability to deploy Verba containers in a stateless configuration. This would involve externalizing the storage of documents and other stateful data. Specifically, we suggest the following enhancements:

  • Integration with object storage: Allow the use of external object storage services, such as Google Cloud Storage (GCS) or Amazon S3, for storing documents and vector embeddings. This would decouple the application's data from the container's lifecycle.
  • External database support: Enable the configuration of an external database (e.g., PostgreSQL, MySQL, or a cloud-native alternative) to manage application state, metadata, and other persistent information that is currently handled internally.

By implementing these changes, multiple Verba instances could share a common data backend, allowing for seamless load balancing and a more robust, scalable deployment.

Additional context

Adopting a stateless architecture would align Verba with modern cloud-native deployment practices, making it easier to manage in container orchestration environments like Kubernetes. This change would significantly enhance Verba's suitability for enterprise-level applications and high-traffic scenarios. Thank you for considering this important feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions