Cumulocity - where to store the configuration of multi-tenant microservice?

Question

Apparently the best practice for storing microservice config settings is in the tenant options.

But I have a use case where the microservice is multi-tenant and I want a common configuration for all tenants stored in one place.

I got a tip to use the tenant options of the tenant that is the microservice owner (see application owner, https://cumulocity.com/guides/reference/applications/#application). I'm thinking of a solution along these lines - on startup, the microservice looks up the id of its owner tenant and looks for config settings in the tenant options. Is this a viable approach and is it safe to assume that the owner tenant is subscribed to the microservice, so that the service has read privileges?

score 2 · Answer 1 · answered Jan 03 '19 at 10:20

2

Technically it is not given that the owner tenant is subscribed to the microservice as well. You will just need to ensure that.

If you want to have a common configuration the owner tenant is the best place.

answered Jan 03 '19 at 10:20

TyrManuZ

2,039
1
14
23

Thanks! In the case of a multi-tenant microservice, what determines the owner tenant? Is it the tenant that the microservice is initially uploaded to? – Mihail Kostira Jan 03 '19 at 13:22
2

Yes, it is the tenant where you create the application in. – TyrManuZ Jan 03 '19 at 17:42

Cumulocity - where to store the configuration of multi-tenant microservice?

1 Answers1