Skip to content

Title How are teams organizing Prisma in large codebases with 100+ models? #29643

Description

@Saif0933

Question

In small projects, it's easy to keep Prisma queries inside services, but in larger applications with dozens of modules and hundreds of queries, how are teams organizing Prisma access?

Are you using repositories, domain services, query builders, or keeping Prisma directly in the service layer?

I'd love to hear real-world patterns from teams running Prisma in production.

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