AEMaaCS Scaling with images

[nsvsrk]

Hi all,

AEMaaCS  has a dynamic architecture with variable number of images.

The architecture is scaled up/down based on actual traffic and actual utility.

What does an image contain exactly?

If it is an entire AEM server, it results in a huge duplication with number of images.

Appreciate your replies.

Thanks,

RK.

[arunpatidar]

Hi @nsvsrk 

Please check https://suryakand-shinde.blogspot.com/2022/01/aem-as-cloud-service-architecture.html 

[nsvsrk]

Hi Arun,

This link leads to a huge page.

For now, all I need is what an image contains exactly please.

Thanks,

RK

[arunpatidar]

Hi @nsvsrk 

Image binaries are stored and handled out of AEM

Please check this as well

https://cqdump.joerghoh.de/2021/03/08/aem-as-a-cloud-service-and-the-handling-of-binaries/ 

[MukeshYadav_]

Hi @nsvsrk ,
The infrastructure is managed by AEM.
We don't need to do much however few limitation which are caused by auto scaling are as follows:

• Not getting dedicated IP to get whitelisted by other system.
  To overcome above issue we get egress IP and need to route all service call through the same.
• Sticky session issue which can be managed by centralised cache is required

Thanks

[Jörg_Hoh · Accepted solution]

I assume that with image you refer to "docker images" or other cloud-native technologies which use immutable images to run containers.

The images contain the entire immutable part of the AEM instance, starting with the JVM plus the immutable parts of the repository (/apps and /libs). 

[kautuk_sahni]

@nsvsrk Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!