The cloud native landing practice of using rainbow for Tuowei information

I am from Tuowei information cornerstone Research Institute PAAS Team Golang Engineer Dingpeng , At the same time, I am Rainbond Community TOC One of the members .

Our team is mainly responsible for the selection of cloud native application platforms , Construction and development , So as to shield the infrastructure at the bottom , Hosting our microservice applications on the Internet , It is convenient and efficient to help the cloud native landing of services in the enterprise .

Company profile

Tuowei information is a leading provider of integrated software and hardware products and solutions in China .

1996 Founded in ,2008 Annual listing （002261.SZ）, With Hunan as its headquarters , In Beijing, 、 Shanghai 、 Shenzhen and other places have branches , staff 4000 More than . The business covers the digitalization of government and enterprises 、 Intelligent Computing 、 Hongmeng ecology , Covering the whole country 31 Provincial Administrative Regions 、 overseas 10+ Country , Focus on digital government 、 Operator, 、 The test 、 traffic 、 manufacture 、 Education and other key fields and industries , Over service 1500 Domestic enterprise customers , Provide them with full stack domestic digital solutions and one-stop comprehensive services of full life cycle .

Tuowei information is determined to become an innovative technology enterprise , From operators to digital government 、 The test 、 manufacture 、 traffic 、 Education and other industries and fields , Continuous intensive cultivation IT Software domain .

PAAS Before

Using an easy-to-use PAAS Before the product , The service deployment methods of our teams are not uniform ：

• A The team applies for ECS , Self built jenkins Deploy the application directly to the server ;
• B The team applies for ECS , Use kubeadm build K8s colony , The development member compiles the image , Operation and maintenance members prepare application declaration files for deployment and maintenance ;
• C The team ...

It can be seen that , There are many problems in the current application operation and maintenance management mode ：

1. The chaos of cloud resource management ： Expense statistics are troublesome , Low resource utilization ;
2. The chaos of team application management ： Multi product library , A variety of supporting management software ; Unable to visually manage the application lifecycle , Monitoring issues , Log problems ;
3. Focus of operation and maintenance ： Focus on resources for operation and maintenance , It takes human creativity , The focus should shift to the application itself , Pay more attention to business innovation ;

PAAS demand

In order to solve the confusion of current resources and Application Management , We need a PAAS platform . This PAAS Platform what we expect it to have ：

• Easy to use ： No developers are needed , Operation and maintenance personnel spend a lot of time and energy learning application management , Cloud deployment and other knowledge , Achieve rapid application delivery , Continuous delivery ;
• automation ： It can manage the whole application life cycle , From source code to accessible services , To the log , Monitoring can be displayed on the platform ;
• visualization ： Application lifecycle can be managed , From the basic application deployment , Scroll to update , Stop etc. , Up to the log , monitor , Scalability, etc , Visible and easily managed on the platform ;

The selection Rainbond

In order to speed up PAAS The pace of platform construction , We decided to stand on the shoulders of giants , From the community to Several PAAS Products are screened . Compare its advantages and disadvantages , Choose the one that better meets the needs of our team —— Final Rainbond Stand out .

Rainbond The advantages of ：

• Application centered design concept , It is really easy to use , Shielding infrastructure concept , Let the development team focus on the business itself ;
• Relatively complete automation capability , Complete visual management capability , Basically meet the requirements of log monitoring function ;
• Intuitive display of microservice topology , Use service grid governance to achieve local access , Reduce service PAAS Configuration changes for （ It was an unexpected surprise ～）;
• The app store offers common software , Help with one click deployment .

besides ,Rainbond It also has the ability to surprise us ：

• Application cross cluster , Rapid replication across teams , Make it possible to deploy efficiently in multiple environments ;

• Complete cluster side components , gateway , journal , Even the product warehouse （ alternative ）, bring Rainbond It can completely provide the ability of application management ;

• Customize the initialization container and SideCar Container capacity , Pluggable way to provide additional capabilities for components ;

Rainbond practice

We use Rainbond Build component rendering ：

1. Visual component topology and component dependencies , And the resulting localized access between interdependent components

2. Full lifecycle management of components , Easy configuration of basic setting resources required by components

3. Efficient gateway configuration center , It is no longer necessary to log in to the cloud platform console frequently to configure load balancing

Rainbond It's easy enough to use, and we don't need to explain how to use it to build and manage components .

Our experience in other fields .

Single domain name multi routing service

The default component is enabled http Port to get such access url：

• a Components ：http://a.apps.example.com

• b Components ： http://a.apps.example.com

And here's what you expect url：

• a Components ：http://apps.example.com/a

• b Components ：http://apps.example.com/b

Then you can use Rainbond Managed PathRewrite function ：

Custom plug in

be based on Rainbond Pluggable design of plug-ins , We can customize the plug-in service .

File management plug-in

You may have the need to upload files to the component container , Thanks to the Rainbond Customize the functions of the development plug-in , You can develop plug-ins to implement file management plug-ins for components , You only need to install plug-ins with file management capabilities for your components , Then create a shared storage of the target directory for the component , Then open the component port , The file management of component container can be realized . Like the image below

Creating plug-ins

Configure plug-in environment variables

Open plug-ins

Create shared storage

Opening http gateway

Data middleware management plug-in

Deployed such as MySQL,Redis Data middleware , There is no ready-made management software , Or it cannot be opened externally at present tcp port , Then you can base on dbgate This open source software is used to develop a data middleware management plug-in .

I believe you have already drawn inferences from one instance , No more examples .

Last

Rainbond So far we've iterated to V5 Big version , As an easy-to-use PAAS Cloud native application platform , The function also tends to be complete , We also look forward to Rainbond Can develop better and better .

Thanks to the Rainbond Community support for , We are using Rainbond Everything went smoothly ,Rainbond It really helped our team make a smooth transition to the cloud native application management stage , Reduce the energy spent on cloud resource management , Instead, focus on the application itself .

But in the process of using, we encounter functions bug Or better practice , We also advocate that the team actively submit issue, Or troubleshooting , This is a point of the open source health cycle .