- Join the happy R&D team at Koderover to build the world’s leading new open source software delivery products from China
- Link to the official WeChat account of the original text
Having experienced the process-driven 1.0 era and the tool-driven 2.0 era, software development has entered the digital business-driven 3.0 era, which has become the lifeblood of enterprise survival. “Build roads if you want to get rich.” Zadig, an open source cloud-native software delivery product, is about building the road to the enterprise so that software engineers stop doing the dirty work of building the “highway” and focus instead on what they do best: building the digital “sports cars” of the business.
Since V1.2.0 was released in early July, Zadig products are 100% open source. What can Zadig do for me? How does Zadig help engineers get out of the “5 minutes to develop, 2 hours to go live” trap? What is the design principle of Zadig, what is good about it, does it suit you?
https://www.bilibili.com/vide…
Today, software delivery requires new thinking
My partner Grant was an old programmer in the mid 90s. In those days, they made PDA mobile game such as Romance of the Three Kingdoms and Journey to the West. One developer, one QA, one artist, one month, the code was closed and burned into the IC card and inserted into the PDA and they could only play by themselves. Today mobile game is the result of hundreds of people working on it over the years, and the complexity has increased exponentially. Not only games, online has happened in all walks of life; Imagine that the complexity of software has increased exponentially, and yet most organizations are still using the same development model as they were 20 years ago. How fast?
In today’s software, microservices architecture is widely used; Microservices make writing code more efficient, but they also increase the complexity of verifying code, and in fact, the way most organizations are doing it today, half of development time is spent doing things other than writing code. It’s like asking Tesla not only to build the best electric cars, but also to build roads. Isn’t that weird?
In real development, sending code online involves a lot of dirty work similar to road building, such as service debugging, inter-service coordination, integration verification, environment preparation, release testing, etc. In particular, the test environment is not stable and not enough, people have to wait for each other, software can not be stable, fast iteration.
Validating software requires new thinking. Here’s how we think:
What new opportunities do new technologies bring? For example, as container technology matures, K8S NS can support a one-click environment to pull up, build and automatically deploy publishing services in parallel.
What new ideas can microservices architecture bring to the systematic design of software delivery? The tools most organizations use today were originally designed to serve only a small part of the process of bringing code online (Jenkins for build; GitLab to the code warehouse, etc.), and microservices are prevalent today. Why not start with the global process of software product delivery and design a more suitable product-level delivery approach based on the microservices architecture?
It is these new things in the cloud native era that allow us at Koderover R&D to see the future of software delivery!
Today, you need a software delivery framework that belongs to the cloud native era
Zadig is a CI/CD product independently developed by Koderover team based on K8S technology. It is an enterprise-class cloud native solution for the global delivery of micro-service products. We focused on one problem: how to eliminate the pain point of software validation once and for all. Through the headlines, tencent, seven NiuYun thousands of iterations, the code, and other enterprises over the years, today’s Zadig micro service architecture has become one of the best software delivery plan, help enterprise one pace reachs the designated position has a strong software engineering delivery infrastructure, let your software team is no longer the toes, to become the star of the enterprise, the core, profit center!
Zadig did all the dirty work of verifying software
Today, the dirtiest part of software development is preparing environmental validation code, something Zadig is particularly good at. Zadig is designed for development, testing, operation and maintenance engineers. By using the cloud native verification infrastructure provided by Zadig, developers can automatically build, deploy, Debug self-test and co-tune services after writing the code. Test engineers can do automated test management, operation, analysis, provide automated verification workflow, test verification of micro-services ahead of time; Operations engineers can provide microservice management, service choreography and environment governance capabilities to the entire R&D team.
In the headlines, tencent, seven NiuYun, long-term practice, according to the code, and other enterprises after using Zadig, engineers started in the development of the introduction of automated ability, in the circumstance that does not extend the working day, effective development time exponentially, software Bug rate dropped significantly, higher stability, iterative speed obviously, everybody also more happy.
In today’s digital age, it’s not that hard for digital businesses to grow quickly and innovate profitably: engineers are happy, and software iterates efficiently and with good quality.
Zadig Design Idea: Developers as the center, with new technologies and new perspectives
In tool design, the starting point is very important. At the beginning of the design of Zadig, we started from the pain point of micro-service delivery, so that engineers could focus on the innovation of business software comprehensively, instead of wasting time on the dirty work of online operation, such as service deployment, environment finding, service arrangement and so on. Zadig takes an overall view of the process required for the launch of software products from the perspective of cloud native. With the help of the ability of cloud native, Zadig pulls up the environment, clarifies the start-stop sequence and dependency relationship of micro-services in the product composition, and realizes efficient verification and launch. The Zadig design is more suited To an end-to-end product-level delivery approach based on a microservice architecture.
By contrast
Jenkins, Gitlab and other related tools have their beginnings in addressing efficiency issues at one point in the development process. To deliver based on these tools, which are mainly extensions to Jenkins/Gitlab products, engineers actually still spend a lot of time on things related to Infra.
Most cloud manufacturers start from the process and management tools to build a unified platform and provide family bucket services. For enterprises, the burden of process transformation will be relatively heavy, and there is also a certain risk of vendor lock-in.
In the open source community, there are many excellent single-point oriented general tools or frameworks, such as Tekton/Argo and OAM/ Kubvela in the cloud native domain. However, these are mainly from the operational and infrastructure perspective, which are flexible, but require a lot of secondary development and high learning cost.
Today, Zadig is the only enterprise-class cloud-native solution that provides global delivery of micro-service products without engineers doing the dirty work associated with Infra.
Zadig features
Zadig takes products as the delivery unit: The product is composed of many micro-services, and the code and configuration of micro-services can come from different code silos and projects. Zadig can handle the start-stop sequence of services, service sharing, micro-service dependency processing, etc., based on Kubernetes NS one-button replication environment. Other solutions cannot solve these pain points completely. Zadig is more engineer-friendly: it is directly oriented to front-line developers, with no additional learning burden and no need to understand CI/CD concepts. One click environment pull, microservice co-tuning and automatic validation are the highlights. Zadig is eco-friendly with extensive integration of excellent tools: We believe in the power of openness, there are a lot of great tools being used by developers in the community, Zadig doesn’t try to solve all the problems, only do the deliverable part that we are best at, and connect extensively with our ecological partners. Requirements tools like JIRA, build tools like Jenkins/ Gitlab CI, deployment tools like Helm, some test services like Tekin, security tools, etc. Zadig wants to be the nexus of software delivery, helping the business iterate quickly while serving developers well. It is also important to note that Zadig has been successfully proven by benchmark customers such as Byte, Qiniu, Fyma, Tencent and other rapidly growing and outstanding companies. It is a mature solution with enterprise class and proven feasibility.
How does Zadig work? The business architecture diagram is shown below
Is the migration cost of using Zadig high?
To put Zadig to work, it’s easy: Zadig native supports the mainstream tools Jenkins/GitHub/GitLab and many cloud manufacturers, and our system itself does not define any paradigm, to achieve the true cloud native unbound, in other words, users feel bad to use at any time can leave, engineers use it is actually no feeling, Automatically build, deploy, and validate at the IDE/ codebank level without having to worry about the system’s existence. Of course, the existing environment of the enterprise is complex and diverse, and we are also very willing to enter the enterprise to do technical exchanges to enrich our understanding.
Zadig: Iterative tools for software delivery 3.0
Through the whole history of software delivery, our observation and summary divide software delivery into three times: 1.0 process-driven era: tools like IBM’s early IPD process push, foreign tools like CA and Electric Cloud; In the form of process string tools and people, mostly in the form of platforms.
2.0 Tool-driven era: Improve deliverability based on a single point of tools such as Jfrog, Artifacts management in the delivery field, Jenkins CI tools, Tekton/Argo on the operations-oriented side, etc., in the last few years, focusing on the efficiency of one link in the delivery chain.
3.0 Digital business driven era: With the booming development of container technology and the wide application of micro-service architecture since 2017, digital business accounts for an increasing proportion of today’s enterprises, and software delivery has entered the 3.0 era driven by the delivery of digital business and the emphasis on developer experience. Only when new tools are natively embraced and loved by developers can software delivery really speed up and stabilize, driving the delivery of products in digital form.
The Zadig
Through many years of thousands of iterations in enterprises including Toutiao, Tencent, Qiniuyun, non-code and so on, today’s Zadig has become the best R & D delivery solution for micro-service + Kubernetes technology stack team, while seamlessly compatible with any R & D team’s existing delivery tool chain and R & D process. Seamless integration with GitHub/GitLab, Jenkins, and several cloud vendors helps the team build strong DevOps and CI/CD infrastructure in one step, transforming the cloud from native to productive.
Zadig itself is an open source distributed continuous Delivery product designed and developed based on Kubernetes. It provides developers with a cloud-based native operating environment that supports local collaboration, microservice parallel construction and deployment, integration testing, and more. Zadig builds in best practices for complex business scenarios such as Kubernetes, Helm, Cloud Host, and Large Volume Microservices to generate automated workflows for engineers with one click.
Welcome to Open Source
Github.com/koderover/zadig | source
Koderover.com | website
space.bilibili.com/502473428 |Bilibili
Gitee.com/koderover/zadig | source
Blog.csdn.net/koderover | CSDN blog
My.oschina.net/koderover | source Chinese blog
Zhihu.com/org/koderover | zhihu
Welcome to Star, Fork, Watch! Discuss and communicate with many developers to build open source community!