There is an enhancement request, with a workaround, here.

(IMO, this is a bug.)

I just upgraded our deployment on Business Cloud from 1.36.4 to 1.36.8, and it was down for nearly 5 minutes.

As far as I know, there were no schema changes. Why does it take so long?

You can't expect customers to pay over a thousand dollars a month just so that their authentication system doesn't go down for a substantial amount of time.

Is this something to do with the current stack? Java? Surely it's just replacing some files and then maybe restarting the app? Which part is taking the most time? Can certain things be skipped during the startup process?

Are there plans to improve this situation? (I don't mean full n-1, just a substantial improvement in upgrade time for updates with no changes to the database.)

The latest templates use lookupLoginMethod(clientId) and not just loginMethod.

I just upgraded our deployment on Business Cloud from 1.36.4 to 1.36.8, and it was down for nearly 5 minutes.

As far as I know, there were no schema changes. Why does it take so long?

You can't expect customers to pay over a thousand dollars a month just so that their authentication system doesn't go down for a substantial amount of time.

Is this something to do with the current stack? Java? Surely it's just replacing some files and then maybe restarting the app? Which part is taking the most time? Can certain things be skipped during the startup process?

Are there plans to improve this situation? (I don't mean full n-1, just a substantial improvement in upgrade time for updates with no changes to the database.)

There is an enhancement request, with a workaround, here.

(IMO, this is a bug.)