Good Morning Folks,
I have had much success hosting DNN on an Azure Web App for a couple of clients. Some of them have inquired about having the site run on multiple servers to avoid downtime. In Azure terms, I believe this is called scaling out.
Does anyone have experience with this, or documentation, on how to do this? I believe in the old DNN terms it was called a webfarm but I have no experience with that. Aside from the web app, is the database usually scaled out too so that it can be redundant and synced too?
Thank you in advance for your guidance.
--Phil
This can be done, but it's not fully supported by out of the box (yet). Some third party modules help with this - both nBrane and Intelequia have solutions and there are probably others. DNN Evoq supports it, too.
When I've seen it done, the database server tends to be scaled up (more power), and the web boxes are scaled out (more servers).
I remember running into issues with a 3rd party extension (OpenContent) due to it's use of Lucene.net for content indexing, so we ended up scaling our instances up rather than out. It's been a while since then, so OpenContent might not have those issues anymore.
Thank you for this super valuable info! Sorry I didn't see it earlier, but I appreciate you sharing your experience.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.