> Then later you only change #2 if you need more modules or you’re updating the runtime. This is an excellent point, albeit one more thing to think about (whic

> Then later you only change #2 if you need more modules or you’re updating the runtime. This is an excellent point, albeit one more thing to think about (which can still be worth it). > What makes sense seems to be very situation specific. This is true, honestly the variety of the configurations out there (e.g. dynamic scaling, where the base layers won't benefit from the ability to cache things, or PaaS solutions where nodes might change for different deployments) makes me doubt the usefulness of my post. Guess that's why there is no one best solution for ALL circumstances.