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 multi-tenant #1090

Open
1 of 2 tasks
kenklin opened this issue Dec 12, 2022 · 2 comments
Open
1 of 2 tasks

Support multi-tenant #1090

kenklin opened this issue Dec 12, 2022 · 2 comments
Labels
DataStore documentation Improvements or additions to documentation feature-request New feature or request p4

Comments

@kenklin
Copy link

kenklin commented Dec 12, 2022

Describe the feature you'd like to request

Amplify DataStore with Multi-tenancy

As a SaaS software company, we have customers whose data not only needs to be protected from each other, but also need finer access for different employees within the company. Furthermore, our professional motorsports team customers need software that is local-first, so that their data may be manipulated, viewed, and analyzed by our software in a standalone fashion on their laptops (Electron) and mobile devices (and web), later to be backed up to the cloud and synced with other team engineers. We work with SRO Motorsports, which AWS is a title sponsor.

At first glance, Amplify DataStore's selective sync with AppSync and DynamoDb seemed like a promising technology to implement local-first data with cloud sync, but we then realized in our discussion with AWS staff on Discord that multi-tenancy was not easily provided out of the box.

Describe the solution you'd like

Multi-tenant local-first data base that can sync with cloud, running on

  • Windows & Mac Desktops (Electron),
  • PWA,
  • Mobile

We'd like to see a complete front-to-back multi-tenant example, from a customer user's authentication in an Amplify app, to DataStore read/write, AppSync, to DynamoDb.

Describe alternatives you've considered

We've read about several including those mentioned here. We are currently experimenting with Couchbase Lite and may also try Firebase.

Additional context

No response

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request

Would this feature include a breaking change?

  • ⚠️ This feature might incur a breaking change
@Rudgey84
Copy link

Rudgey84 commented Feb 9, 2023

I support this request. Also looking for a multi-tenancy solution for users to sign in based on email domain so compant data remains separate only sharing the UI.

@josefaidt
Copy link
Contributor

Hey @kenklin 👋 thanks for raising this! The multi-tenant request appears to be a duplicate of a few other issues around the topic:

I'm going to mark this as a documentation feature-request to look into adding an example like this!

@josefaidt josefaidt added documentation Improvements or additions to documentation and removed pending-triage labels Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DataStore documentation Improvements or additions to documentation feature-request New feature or request p4
Projects
None yet
Development

No branches or pull requests

4 participants