TarMK Vs MongoMk

Avatar

Avatar

Sam205505050

Avatar

Sam205505050

Sam205505050

15-10-2015

Hi,

As per my understanding, TarMK is faster than MongoMK due to the fact that segments are immutable and because of this it is easy to cache frequently accessed segments(TarMK). MongoMK is recommended where scalability is important. 

Now, TarMK is not suitable when we use clientcontext. And the reason is, if we use multiple TarMK enabled publisher then all the publisher does not sync because AEM 6 does not support clustering. Now lets say one request coming from Load balancer which updates clientcontext cookie on a particular AEM instance  but subsequent request will not come to same  AEM instance unless we use sticky session.So, in this case user will see different behavior if sticky session is not used.  Again I was told that if we use  sticky session then again it increases loads on particular AEM instance. Anybody has good/bad experience on this? 

So I would like to know best practice while using clientcontext with TarMK. Is it recommended to use MongoMK with clientcontext even though TAR is faster? What are the other parameters I should consider?

Thanks for your help!

View Entire Topic

Avatar

Avatar

bsloki

MVP

Avatar

bsloki

MVP

bsloki
MVP

15-10-2015

you mean delivering pages from Akamai CDN ?? It will work as client context is built via JS if you have included in your templates.