When developing a package, can I rely on Umbraco backoffice being a single server/application?
Based on load-balancing advice it seems that backoffice is expected to be on a single server. Are there any cases when it wouldn't be?
I'm developing a backoffice plugin so I need to know whether to store my (transient) state in application memory, or whether to share it through a database.
as i recall from the fab loadbalancing workshop on codegarden, the admin side of umbraco should always be on 1 (and only 1) server. Otherwise you'll run into a lot of trouble.... (although i have no idea what kind of trouble, i'm not eager on finding out the details myself ;-) ).
I can confirm from personal experience that allowing editing and publication from multiple servers can cause a real headache and a lot of confusion with different content appearing on different servers so we now force all editors onto a "master" server in the load balancer. Currently we do this via rewrite rule to redirect back office requests to the "master" server.
Each of the servers behind the load balancer can be accessed via a unique subdomain so we check this in the rewrite rule and if not the correct one we redirect them to where we want them.
I'm just in the process of upgrading the site to 7.4.3 and so not sure if there is anything new in there with the introduction of the new server registration stuff that can help with forcing an editing server?
Yes, as the guys have already answered Umbraco should only be accessed on one server. It's possible to access it from multiple but that is not supported and can cause corruption.
If your values are only used on the back office then you will be ok. You could also use a CacheRefresher to update memory cache on multiple servers as Dave mentioned already.
When developing a package, can I rely on Umbraco backoffice being a single server/application?
Based on load-balancing advice it seems that backoffice is expected to be on a single server. Are there any cases when it wouldn't be?
I'm developing a backoffice plugin so I need to know whether to store my (transient) state in application memory, or whether to share it through a database.
Andrey,
Not sure on the answer to this, but I'd like to know too?
Possibly the best person to ask is Jeavon from Crumpled Dog, I've tweeted your Our link and tagged him for you!
Let's see what he says!
Cheers, Jon
Hi all,
as i recall from the fab loadbalancing workshop on codegarden, the admin side of umbraco should always be on 1 (and only 1) server. Otherwise you'll run into a lot of trouble.... (although i have no idea what kind of trouble, i'm not eager on finding out the details myself ;-) ).
Gerty
Good point Gerty! :-D
I can confirm from personal experience that allowing editing and publication from multiple servers can cause a real headache and a lot of confusion with different content appearing on different servers so we now force all editors onto a "master" server in the load balancer. Currently we do this via rewrite rule to redirect back office requests to the "master" server.
Simon, do you keep master on separated subdomain / domain or doing this some other way (server registar etc.)?
Each of the servers behind the load balancer can be accessed via a unique subdomain so we check this in the rewrite rule and if not the correct one we redirect them to where we want them.
I'm just in the process of upgrading the site to
7.4.3and so not sure if there is anything new in there with the introduction of the new server registration stuff that can help with forcing an editing server?Cheers, Simon
If youre package needs some caching that is also used in the frontend than you need to implement a cache refresher.
See this one for a good example : https://github.com/Jeavon/SEOCheckerCacheRefresher
Dave
Yes, as the guys have already answered Umbraco should only be accessed on one server. It's possible to access it from multiple but that is not supported and can cause corruption.
If your values are only used on the back office then you will be ok. You could also use a CacheRefresher to update memory cache on multiple servers as Dave mentioned already.
Thanks! That simplifies my life a lot.
if you do try and have back office across mulitple servers .. very bad things will happen.. eventually...
is working on a reply...