Home > database >  Store tenant preferences in a multi-tenant app in DynmoDB or SSM
Store tenant preferences in a multi-tenant app in DynmoDB or SSM

Time:12-09

I have a multi-tenant application and the backend comprises of the microservices. The tenant admin will have a preferences page on the UI that can store system preferences for the tenant (i.e all users of the tenant).

I am thinking about what the best place for storing this would be?

SSM or Dynamo? Any trade-offs here for this use case?

we have a tenant microservice or we could create a system preferences microservice to store the preferences. I am trying to avoid all cross-service communication so the user of each tenant will get all the preferences on login and will send them back in the header. Should we continue to store the preferences in the tenant DB or system preferences microservice is the way to go?

CodePudding user response:

Configuration variables usually are stored in SSM Parameter Store. For one its free. From docs:

Parameter Store, a capability of AWS Systems Manager, provides secure, hierarchical storage for configuration data management and secrets management.

SSM Parameter Store also integrates natively with many other services. For example, you can seamlessly use them to pass secrets to ecs containers.

  • Related