So, what is proposed is to create another application for staging service structure and routing traffic, whether it is to gradually move users to the new version of the instance, or just flip the switch And send all traffic to the new version at once.
We need a solution that would both support Webapps and Service fabric.
Providing patterns and experience for stateful services would be
great.
Reference
A.Web Apps Slot Exchange
https://azure.microsoft.com/ en-us/resources/videos/azure-websites-deployment-slots-for-staging-sites/
B. Continuous delivery pipeline
PS:
I know that swapping is meaningless for stateful services. Therefore, if we want to keep your data and To maintain its consistency, you must perform a rolling upgrade.
We have built a Web API on the service structure, and there are also some web projects in the web application in Azure. We hope to easily exchange back to the old version of the application and improve the CD pipeline when deploying.
So, what is proposed is to create another application to temporarily store the service structure and route traffic, whether it is to gradually move users to the new version of the instance, or just flip the switch and bring all the traffic Send to the new version at once.
We need a solution that would both support Webapps and Service fabric.
Providing patterns and experience for stateful services would be< br> great.
Reference
A.Web Apps Slot Exchange
https://azure.microsoft.com/en-us/ resources/videos/azure-websites-deployment-slots-for-staging-sites/
B. Continuous delivery pipeline
PS:
I know that swapping is meaningless for stateful services. Therefore, if we want to keep your data and keep it consistent , You must perform a rolling upgrade.
Consider using Azure Api Management, which now has proper support for Service Fabric (check their trello). It should be resolved The version control of the two, because it is agnostic to the external technology and the underlying technology, except that it does not provide a gradual increase in traffic.