Hello, @SURAJ_BELVADI NY State of Health site
Given a Reasons table with various reason types, it’s better to use one Reasons collection for the following reasons:
Pros:
Simpler queries and management
Easier to add new reason types
Better indexing and replication
Unified CRUD operations
Cons:
Potential performance impact if the collection grows
Queries need to filter by reason_type
Multiple Collections:
Pros:
Clear separation of data
Potential performance gain for very large datasets
Cons:
Increased complexity in management and CRUD operations
Redundant operations for each collection
Scalability and replication issues
Recommendation:
Use one Reasons collection. This approach simplifies management and is sufficient given the small dataset size.
I hope this suggestion will be helpful for you
Best regards
chris wright