Entity and Team Limits in Cortex
Cortex offers flexibility when it comes to managing entities, teams, and owners within its platform. It's important to note that there is no documented hard limit on the number of teams that can be listed as owners for a service in Cortex. Users can assign multiple teams as owners to a service, and the user interface supports adding multiple teams sequentially without replacing previous selections.
Considerations for Large Numbers of Entities
While Cortex doesn't impose strict limits, it's crucial to consider performance implications when dealing with a large number of entities or teams. In scenarios with very large numbers of owning teams, such as in a monorepo, users should be mindful of potential performance and manageability impacts. Although there is no explicit technical or UI limit documented, it's advisable to consider these factors when scaling up your Cortex implementation.
Team Membership and Access Control
When managing teams and ownership in Cortex, it's essential to understand how team membership affects access control. For ownership to be considered valid and for teams to be counted in scorecards and CQL queries, the teams must have at least one member. Teams with no members are not treated as valid owners in certain reporting and query contexts. This could potentially affect your access control logic if you rely on empty teams as owners.
Best Practices for Large Volume Uploads
If you need to assign a very high number of teams or entities, it's recommended to reach out to Cortex support for guidance. They can provide best practices tailored to your specific deployment and advise on any potential soft limits that may apply. When uploading large volumes of data, it's best to connect with Cortex support so they can partner with you on load testing to ensure optimal performance and functionality.