When you make some changes on the server and you warn that there will be annoyances while the changes are being completed, there is always someone who sends you an email with the title in capital letters asking for urgent help because something is wrong.

Well, it’s kind of normal.

You need to put an infrastructure in place, so changes are transparent for end user.

On my side, I’m using Azure slots with hot swap. So far so good.

Maybe 1-2 requests getting dropped in rare cases, but usually the users don’t even notice updates (Except if there is something visual ofc)

I know is normal :) i am just telling there is always someone who doesn't read the warning.

@NoToJavaScript that might work for external sites but you rarely get to build that stable on internal tooling.

Especially when your not based in USA and working with sensitive data that cannot be put into any us based cloud due to the lack of protection from us authorities :/

It used to be ok until us changed their laws to include any information stored on any server belonging to a us company even if the server physically is in the EU.

@Voxera I think even locally you can implement something similar. But I get the “Noone will allow so much dev time for 5 min downtime at each deploy for internal app” argument.