document service limits (HA / scalability)

[wkloucek]

• search can not be started multiple times (and there is no plugin replacement), so use in HA / scaled installations is limited.

• idm cannot be started multiple times. Should not be used in HA / scaled installations, but instead replaced by an LDAP server that supports HA / scaling. Even if no HA / scaling is needed, the IDM is only supported up to ~200 (??) users.

• idp cannot be started multiple times. Should not be used in HA / scaled installations, but instead replaced by an OIDC provider server that supports HA / scaling. It has a bare minimum feature set (eg. you cannot easily revoke single sessions)

• store cannot be started multiple times. We are still looking into removing or making the store scale, see Investigate in store usage and signing keys ocis#3913

• nats cannot be started multiple times. Should not be used in HA / scaled installations, but instead replaced by an NATS installation that is HA / scaled.

see also owncloud/ocis-charts#77 (comment)

[mmattel]

What about creating a "Deployment Limitation" page describing the above issues?

instead replaced by an NATS installation that is HA / scaled.

need more details on that and what is meant.

[wkloucek]

What about creating a "Deployment Limitation" page describing the above issues?

That could be an option. Though "Limitation" is not too nice. I rather would call it "Advanced Deployments" or something similar positive. (It's not a limitation for most of the service, but a design choice.)

instead replaced by an NATS installation that is HA / scaled.

need more details on that and what is meant.

Referencing NATs documentation should be enough, eg. https://docs.nats.io/running-a-nats-service/configuration/clustering. They also have a Helm-Chart for that purpose, that I'll link in our Helm Chart, too. (see also owncloud/ocis-charts#12)