Wednesday, August 14, 2019

Which is better: large app image or small app image?

I am on a team working on a hybrid cloud platform for networking apps. This platform is based on k8s and it's purpose is to provide the foundation for customer facing apps which provide various network management functions.

One of the issues I am looking into is how to distribute this platform. The idea is a user downloads it and installs it on a Linux systems(s). Now there are basically two ways to support this - 1) a single large image containing all container images, apps, etc that will be needed to complete an install. 2) a smaller download which acts as a seed, which then gets installed. This seed app will download all the other container images and resources needed for an install.

We will support offline install via #1.

My question is which is preferred by an end user for online installs - a large single image (2-20GB range) or a smaller seed image (few MBs) which will download the rest (2-20GB)?

My boss seems to think the smaller seed image #2 is best. I see advantages here, but I also think there are advantages with a single large image - namely getting things upfront and not worrying about download issues during install, and/or corruptions.

The size range is large because what the platform ends up being is up in the air.

Thoughts??



No comments:

Post a Comment