Adobe Ask the AEM Community Expert Session Oct 2016

Editor's Notes

• #8: AEM Licenses Author – content size and no of authors- might prompt multiple authors in active active configuration (or sharded) Complex requirements HA needs Enterprise commit
• #27: Virtual/Physicals : Many installations with virtuals exist – and are successful. But in large scale installations – due to scalability issues – and lack of the Mongo option in prior years – people frequently go to physical author. Many examples exist of this paradigm (Cisco – and other companies of cisco’s size) Linux/Windows : On the surface there does not seem to be any data to support superiority of Linux over Windows – however – anecdotally – there seem to be more examples of Linux based installations. Storage – For Author NAS is probably not a great idea. SAN can usually do the trick on author – but there might be a case to consider attached storage for best performance. For Publish – SAN would be a safer bet, but NAS can also do the job . Dispatcher@Author – Our recommendation is to have it – even if it only alleviates some of the asset caching. There are some caching settings to keep in mind – to ensure the content is fresh. Usually only very small scale installations tend to skip dispatcher at the author. LB @ Publish : Provides maximized fault tolerance. Cisco has this model. However it increases the complexity of the architecture. Especially the clearing of dispatcher cache on activation in publish HA: DR, Multi-DC: For most large scale installations – multi DC is a must, Author can be a bit challenging here – in case of TarMK – DR is also recommended. But there might be some innovative approaches that could be used to optimize the cost of DR. Either by having a small footprint – that can be quickly increased (scaled up if required), or just focusing on author – and having some extended caching settings at DR (servecacheonstale equivalent). Also – it is a good idea to have backups of author, a single publish and the dispatcher – foeasy restore in case all else fails. Caching : Multiple levels of caching – CDN, web server & application server. Tradeoff between performance and simplicity. Application cache is required only if there is a lot of application logic – and dynamic component or other logic. Web server is required if there is a huge amount of traffic that still makes it through to the publish server and there is not enough offload.. HAL DR , Multi DC: Generally all large scale companies need both a DR and multi DC strategy (in addition to a solid back up strategy) CDNs can provide some level of protection
• #30: - Think clearly about how to present this – ITaaS angle may need to be cleared up..
• #31: Over Customization complicates everything - Maintainability – system bloat - Upgrade path -
• #32: Check with Sameer – whether I can share Azure… Make it real -