Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Pool and Bridge Multi-Tenancy Models in AWS SaaS Boost? #542

Open
tichise opened this issue Feb 7, 2024 · 0 comments
Open
Labels
triage Needs categorization and prioritization

Comments

@tichise
Copy link

tichise commented Feb 7, 2024

❓ General Issue

The Question

I am exploring the AWS SaaS Boost project for a multi-tenant SaaS application and am interested in understanding its support for multi-tenancy models, specifically the Pool (multi-tenant) and Bridge models. These models are crucial for our application architecture, and I would like to know if AWS SaaS Boost provides built-in support for these models or if there are recommended approaches to implement them within the framework. Additionally, I am looking for guidance on best practices for leveraging AWS SaaS Boost for these types of multi-tenancy architectures. Any insights or resources related to this would be greatly appreciated.

Environment

  • AWS SaaS Boost Version: Latest

Other information

I am in the process of designing a SaaS solution and evaluating different multi-tenancy architectures. Understanding how AWS SaaS Boost can facilitate or support these models will significantly impact our architectural decisions. Any related documentation, examples, or advice on implementing Pool and Bridge multi-tenancy models with AWS SaaS Boost would be very helpful. Links to any associated GitHub pull requests, Stack Overflow discussions, Slack channels, or any other resources for context would also be appreciated.

@tichise tichise added the triage Needs categorization and prioritization label Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs categorization and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant