Hi ,we have an application in production ,When we receive bug reports from users and fix them, deploying the application while users are actively using will it cause any disruptions ?
Typically, we schedule deployments during non-business hours to minimize any impact on users. Would you give more information or assistance with deployment strategies?
We required to deploy application now asap we fix bugs,suggest me
Hi Sérgio, you are right I was referring to the cloud infrastructures hosted by OutSystems, I forgot onprem sometimes, as most of our customers are having their infra hosted by OutSystems in the cloud.
Hi,
Each production environment has at least 2 front end servers, allowing deploy to production with zero downtime. One by one the front end servers are updated. There is always at least one running.
-- Daniel
thank you, is there anywhere I will get supporting document,
after deployment how the sync between 2 servers will happen, while syncing is there any impact to users who are using application.
how that we are achieving zero downtime.
Hello,Daniel, not all production environments have multiple front-end servers. Obviously, it is highly recommended and if it's an OutSystems Cloud production envionment it will have that configuration, but in a self-managed installation it might not.In a deployment plan all front-end servers are usually updated at once, to update them one by one it would be a kind of balanced deployment and it requires some work to do it like that:https://success.outsystems.com/documentation/11/deploying_apps/balanced_application_deployment/Priya, usually you can deploy to production without issues or downtime.In specific situations or in very highly loaded environments, you might consider a balanced deployment as described in the above link.
thank you @Sérgio Miranda, is there anywhere I will get supporting document,
Hello Priya,
The documentation I already mentioned should help you with questions about how to mitigate impacts during deployments using blue/green strategies.https://success.outsystems.com/documentation/11/deploying_apps/balanced_application_deployment/Regarding "synchronization", during application publishing the new version will be deployed to all enabled front-end servers immediately and loaded in IIS after that as soon as a request for that application module is received.If the deployment fails to a front-end during the publishing, there will be a warning in the publishing log and it will be retried later.Customers using the application might notice the first requests after deployment taking longer to process, how much depends on several conditions.Also, during publishing there might be extra load on the database and the deployment controller, so if these already had high load from user requests (assuming the controller also acts as a front-end server) it can have an impact as well.