Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • I infra-azure-provisioning
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Deployment and Operations
  • infra-azure-provisioning
  • Issues
  • #139
Closed
Open
Issue created Mar 12, 2021 by Krishna Nikhil Vedurumudi@krveduruMaintainer

Issue - Cosmos DB Limitations || Shared throughputs

Cosmos DB's shared throughput cannot be stretched beyond 25 collections. Quoting Azure documentation ->

Azure Cosmos DB accounts using shared database throughput are now limited to 25 collections per database. This will allow for better throughput sharing across collections. Create additional databases with shared throughput and add more collections or add collections to the same database with dedicated throughput.

In OSDU we are currently at 25 collections. So, we have already hit the limitation.

This would require us to re-organize our collections to multiple databases so that they can scale in a better way.

Assignee
Assign to
Time tracking