JSPM

praveen-shareddatabase-separatescehma

1.0.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 9
  • Score
    100M100P100Q58358F
  • License ISC

Reusable SaaS backend package implementing shared database with separate schemas per tenant. Provides logical data isolation, dynamic schema handling, and plug-and-play integration for scalable multi-tenant Node.js applications without managing multiple databases

Package Exports

  • praveen-shareddatabase-separatescehma
  • praveen-shareddatabase-separatescehma/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (praveen-shareddatabase-separatescehma) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

praveen-sharablesaas-differentschema

A reusable SaaS backend architecture package based on Shared Database, Separate Schema multi-tenancy.

This package enables you to manage multiple tenants within a single database while maintaining logical isolation by assigning separate collections/schemas per tenant. It is designed to be plug-and-play, allowing easy integration into any Node.js project.

With minimal setup, you can dynamically handle tenant-based data separation, making it ideal for scalable SaaS applications that require better isolation than shared schema without the overhead of multiple databases.

Features: Multi-tenant architecture (separate schema per tenant) Dynamic collection/schema handling Plug-and-play integration via npm Scalable and modular structure Works with existing Node.js + MongoDB apps

Key Features: Single database instance Separate schema/collections per tenant Logical data isolation Moderate scalability

Pros: Better data isolation than shared schema Cost-effective compared to separate databases Easier tenant-level customization