Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to realize rolling publishing, blue-green publishing and grayscale publishing of micro-services based on Rainbond

2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about the rolling release, blue-green release and grayscale release of micro services based on Rainbond, which may not be well understood by many people. in order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

Overview

There are three common ways to publish micro-services based on Rainbond: rolling publishing, blue-green publishing and grayscale publishing.

one。 Scroll publish

The difference between stateless application rolling update and stateful application rolling update on Rainbond platform:

* * stateless applications: * * when rolling updates, a new instance will be generated first. After the new instance is started, the platform will use the health monitoring mechanism to monitor the port to determine whether the application in the new instance is running properly. Once it is monitored that the application is running properly, it will launch the new application and destroy the old application, thus completing the rolling release process.

* * stateful applications: * * if it is a non-clustered application, the old instance will stop running before a new instance is generated, and when the new instance is updated, the old instance will be abolished. If it is a clustered application, there is no need to worry about service interruption. You can update it in batches. To ensure the operation of the service.

Rolling release practice of Rainbond platform

Here, take stateless applications as an example.

Switch build sourc

Toggle code branch

Re-detection

Number of scaling instances

Start building

At this point, two new instances will be generated to see if the new instance has been created. If the application in the new instance runs properly, the old instance will be abolished and the new version will be launched.

If you look at the construction history at this point, you can roll back to any version that was built successfully.

two。 Blue and green release

Blue and green deployment is a non-stop old version, deploy the new version and then test it, confirm the OK, cut the traffic to the new version, and then upgrade the old version to the new version at the same time.

Blue and Green Publishing practice based on weight using platform Gateway function

Web service binding domain name

Web service domain name weight Web V1www.test.com100Web V2www.test.com0

The switching between versions can be realized by reducing and raising the weight by applying gateway-> access control, respectively.

Unweight Web V1

Adjust the weight of Web V2

At this point, the traffic has been transferred to Web V2 and the blue and green release has been completed.

For more information about application gateways and access control, see Application Gateway access policies.

three。 Grayscale release

Grayscale publishing refers to a release way that can make a smooth transition between black and white. The grayscale release can ensure the stability of the whole system, and the problem can be found and adjusted at the initial gray level to ensure its influence.

Grayscale publishing practice based on weight

Control from the dimension of traffic, such as switching the first 10% of traffic to the new version, and then gradually increase this weight until the weight of the old version is less than 0, that is, the gray release is completed.

Still add the following two HTTP access policies through the Application Gateway-> access policy:

Web service domain name weight Web V1www.test.com90Web V2www.test.com10

Gradually reduce the Web V1 weight as needed, and increase the Web V2 weight until the Web V1 weight is reduced to 0.

After reading the above, do you have any further understanding of the rolling release, blue-green release and grayscale release of micro-services based on Rainbond? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report