I've been taking a look at adding Load Balancing support to Tea Commerce this weekend and I'd love to hear from anyone who has attempted to host Tea Commerce on a load balanced environment.
So far I've created a PR on the Tea Commerce for Umbraco GitHub repo with some updates to setup some ICacheRefresher instances for all the cachable items from within TC and event handlers to trigger the distributed cache invalidation:
I've mostly based my work so far on various other forum posts I've found that mostly talk about the caching layer being the issue, so these updates should fix that (thought it still needs some testing to check the performance when a cache is cleared as we essentially clear whole collection caches when any change occurs).
As I say though, I'd love to hear from others that have attempted to host TC on a load balanced environment, or maybe someone from HQ, to know what other things need looking into / addressing.
Load Balancing Feedback Wanted
Hi folks,
I've been taking a look at adding Load Balancing support to Tea Commerce this weekend and I'd love to hear from anyone who has attempted to host Tea Commerce on a load balanced environment.
So far I've created a PR on the Tea Commerce for Umbraco GitHub repo with some updates to setup some
ICacheRefresher
instances for all the cachable items from within TC and event handlers to trigger the distributed cache invalidation:https://github.com/TeaCommerce/Tea-Commerce-for-Umbraco/pull/72
I've mostly based my work so far on various other forum posts I've found that mostly talk about the caching layer being the issue, so these updates should fix that (thought it still needs some testing to check the performance when a cache is cleared as we essentially clear whole collection caches when any change occurs).
As I say though, I'd love to hear from others that have attempted to host TC on a load balanced environment, or maybe someone from HQ, to know what other things need looking into / addressing.
Any feedback would be fantastic.
Thanks folks
Matt
is working on a reply...