Easy express: we use Zadig to realize 10000 times of construction and deployment, smart operation and maintenance, and release development productivity

Zadig  Really understand operation and maintenance ！

Easy express is a company engaged in expense control and reimbursement  toB  Of  SaaS  Enterprises , Committed to the innovation of cloud products and services in the field of enterprise financial digitization , Using cutting-edge digital technology and advanced creative ideas , Build financial digital intelligence and empower the growth of future financial people . Through agile connection mode innovation and independent research and development “ No reimbursement is required ” The solution provides enterprises with aggregate consumption 、 Reimbursement control 、 Enterprises pay 、 One stop services such as invoice and electronic file management , Provide data decision analysis and support for enterprise industry finance integration , Help enterprises realize cost reduction, efficiency increase and compliance management , Yi Kuai Bao has been paying attention to... Since its early version  Zadig.

background

As the R & D team continues to expand , The production research team has reached  200  Many people ,GitLab CI/CD  It has been unable to meet the increasing needs of researchers ,

Environmental management , Division of authority , Build optimization

And so on, which greatly increases the cost of operation and maintenance , Therefore, we urgently need new solutions to improve our current situation ,Zadig  Became our

Preferred solution

.

The selection

Build deployment flowchart

Pain points

• Multiple groups work together to maintain a set of code , It is difficult to control the delivery image

• Each group needs a full set of environments for R & D and testing , Lack of unified management platform

• Pull the full code at compile time , Packaged builds are extremely time consuming

expect

• When R & D needs
  Quickly pull up a set of environment

• When resources are tight, the environment can be released

• Reduce packaging time , Improve code delivery efficiency

• Access control , Project Independence

analogy

• Choerodon

• Argo/Tekton

• Zadig

In the process of investigation and type selection comparison , We found that  Zadig  That best fits our current situation , It is also the most appropriate choice for us at this stage . Use  Zadig  Of  Helm  The deployment mode can

Effectively solve the deployment of multiple services sharing one image

problem . In Environmental Management ,

R & D can maintain the environment by itself

, Modify the configuration , Greatly reduce the maintenance cost of operation and maintenance , Give Way

O & M has more time to do more useful things

.

More choices  Zadig  The reason of ：

• Support  Serverless  resources ： Put the build process in  
  Serverless
    On , Greatly improve the construction efficiency , At the same time, it saves a lot of costs

• Support data overview 、 Efficiency insight ：
  A smart team will observe
  , This part is an important part for the O & M team to build observability

• Delivery Center ： I understand it as a service snapshot , It can help the R & D team
  Quickly switch versions
  , It really works

to ground

  In the test  Zadig  In the process of , Keep trying to use  Zadig  The functions of , And hope to use it to the extreme . stay Zadig  The initial version is not fully applicable to the current usage scenario of easyexpress , There are also some insurmountable obstacles . However  Zadig  Have an inclusive team , In the process of continuous communication , We also learned about the design concept of some functions , At the same time, they also constantly put forward their own pain points and demands . stay  Zadig  With the help of the team , Our problems were solved in the next few iterations , This greatly encourages us to land  Zadig  The confidence of the , In the end in  Q1  To the production and research team , And received unanimous praise .

At present, we have two main usage scenarios , A simple example ：

Deployment flowchart

Build a flowchart

Just a few months , E-express has been used by the production and research team  Zadig  Nearly 10000 build deployments have been completed .

The goal is

  At present, we are right  Zadig  The use of is still in its early stages , There is also a need to set higher goals . For example, the intervention of testers , How to dock Sonar  scanning , How to make personalized workflow , Use of collaboration mode, etc , I believe these are not just the problems faced by our team , In the future, we hope that  Zadig  Connect with existing systems , Make it work  DevOps  An important part of , Provide sufficient guarantee for the team .

At the same time  Zadig  Offer some slots ：

• During the access process, it is found that  Zadig  Workflow capability is still relatively weak , There is no way to personalize the built image version

• Helm  Make multiple services into one  Helm  package , If there are multiple services sharing one image , Cannot update a single service version independently .

• The built log does not support some minor optimization problems, such as the search function

• Version upgrade is troublesome , We have many clusters , Every time you deploy  Agent  All have to be upgraded one by one , Is not convenient

Conclusion

just as  Zadig  one's wishes , " The engineer  + Zadig =  Business success ", As  Zadig  Users of , From first sight to landing , Yes  Zadig  I also have my own painstaking efforts . You can see  Zadig  Is moving towards maturity , I'm also making progress . The follow-up express will continue to try  Zadig, And give some opinions and understandings , In the future, we will also consider contributing code to the open source community . Finally, I wish us and Zadig  Have a bright future  ~

Zadig, Let engineers focus more on creating ！ Welcome to join  

Make complaints about open source Tucao group

Zadig on Github

 

https://github.com/koderover/zadig

Zadig on Gitee

 

https://gitee.com/koderover/zadig