2回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
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
0
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.
関連するコンテンツ
- 質問済み 8日前
- 質問済み 6年前
- 質問済み 7年前
- AWS公式更新しました 3年前