Should i use one data base per user on AWS RDS for MySQL?
I'm creating an application where each business will have;
- owner which is a user at
some-business-name, - Some information about the business (This part will actually change my app's UI)
- employees(Also users same as owner)
- permissions (for employees. Permissions for owner can't changed)
- customers
- ...
These are all unique to every business!
There is no limit on the number of businesses
I think i need a new database for each business with a unique business name (some_business_name). There is no limit on AWS RDS for MySQL based on https://aws.amazon.com/rds/faqs/ - "How many databases or schemas can I run within a DB instance?". So this should work right?
My question is:
- Is this solution suitable for such an application?
- What are the pros and cons?
- Should i use DynamoDB instead?
- Are there any articles I can use?
I'm new to MySQL, I think every answer will help me a lot. thank you 🙏
NOTE: I have to create this application using aws
- 最新
- 投票最多
- 评论最多
What you are trying to build is essentially a multi-tenant solution on AWS. Although you could have a separate database per tenant, you don't necessarily need to have a separate database per tenant, as that will be very expensive.
Here are some good blogs that talk about building multi-tenant solutions, that you can use as guidance for building what you are trying to build
There is not enough information here to give a straight answer, but probably you do not want multiple schemas. If your application is expected to connect to multiple 'businesses' then you probably want a single schema. If you instead use 'per business' databases, your application will need to change the database context for each query.
相关内容
AWS 官方已更新 2 年前- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
