@zackster thanks for the single mode link explainer https://docs.lucee.org/recipes/single-vs-multi-mode.html - i haven't fully wrapped my head around it yet (still on 5.x) So if i have multiple IIS websites, each has their own application name and pretty much the only thing in Lucee admin is a root mapping and datasource. So In single mode - all websites would run under a single lucee context ... i guess my main question is; exactly which configurations are consolidated in order to know if i'm impacted? Or maybe the inverse, when would you need multiple web contexts? (or maybe that is moot if multi is on the way out ...) (in which case, if you DID need it, would you just run a separate lucee instance for each web site?)

Whether or not this affects you largely depends on whether or not you configure things in the web admins, or if you put it all in the server admin

The way websites are deployed has evolved quite a bit over the years. Mult-Mode was something that was particularly useful for shared hosts where they stuck a whole bunch of websites on a single server, but they wanted to separate out the memory space so that if one website did something weird or crashed, it wouldn't take out the others **. These days the same functionality is really provided using tech like Docker, K8 or others where you can spin up completely separate services per server. That gives you full* separation, including filesystem and settings for a bit added security. Memory foot-print wise, it's nearly the same since Docker/K8 will use common memory space for the running processes.

Of course, having a separate Lucee server per site is the direction most modern deployments have headed, in the days of Docker and containerization. But I understand everyone isn't there.

Everything above is 💯 there are some settings which are compiler settings which can't be set via application.cfc, it's too late once you're running code, which is one advantage of multi mode, as you could tweak them per web context

Yeah, the memory footprint is usually the sticking point. We've had clients with 100 to 200 separate websites and it's just not economical for them to run 200 CF instances.

Everything going into application log is a bit noisy, you can use tag defaults per application to spread them out per site https://docs.lucee.org/reference/tags.html

@bdw429s thanks! that was really the key bit of info i needed. We configure everything in the lucee server admin not the web admin so sounds like it should be ok.

added that hint about server admin to the docs https://docs.lucee.org/recipes/single-vs-multi-mode.html#what-is-multi-mode

@zackster nice, did not know that!

if you see any docs which need clarifying or you want to simply improve something, let me know, or just click the github icon on the page if you want to edit anything