#1 2018-10-27 14:31:09

dualarrow
Member
From: Australia
Registered: 2018-06-28
Posts: 21

mORmot scalability and redundency

I understand you can scale mORmot by having multiple services each on a different server.

Is it possible to have the same service on more than one server (with the database eg MS SQL on a single separate server) to help spread the load of the service ?

Also, if you can have the same service on more than one server is there any way to provide service resilience so that if a service was to stop functioning (eg server hardware failure) so the client could cleanly switch over to another functioning server providing the same service ? I suspect this one may not be easily possible and it may be better to let the client restart fresh.

Offline

#2 2018-10-27 14:41:30

mpv
Member
From: Ukraine
Registered: 2012-03-24
Posts: 1,544
Website

Re: mORmot scalability and redundency

Yes - use some kind of reverse proxy for this (nginx, haProxy, ...)
But in most case DB will be a bottleneck, not a app server. So having app server on more than one server is more about stability, not about scale.

Offline

#3 2018-10-28 01:25:27

dualarrow
Member
From: Australia
Registered: 2018-06-28
Posts: 21

Re: mORmot scalability and redundency

Thanks for the reply.

Thats mostly what I thought would be the case and yes, the question was more about stability than scaling. I'd see scaling as more of having multiple DBs splitting the services across DBs to help spread the load.

Offline

Board footer

Powered by FluxBB