1. Decoupling the Engine to Unlock Pipeline Capabilities When designing a system, we often face a dilemma. Do we contain the complexity and offer a single, easy-to-use capability to the outside; or do we release the complexity and return flexibility to the user? This is a real test of product

1. Why Physical Build Machines Are Needed In the article How to Add a Remote macOS Physical Machine for Jenkins Pipeline Builds, I described how to add a physical build machine in Jenkins. This was not a requirement I made up on a whim — at the time, real ToB commercial customers were actually asking for a solution.

1. What This Article Mainly Discusses Never build a high tower on shifting sand. Business growth and the evolution of business forms both need solid, powerful IT systems to support them. Business content is transparent to the market, but IT systems cannot be built to perfection overnight. In the future, competition between companies will mainly come from competition between their IT systems, and the ability to respond quickly to business requirements will be the key to winning.

1. What Is Cloud Native Cloud native is a rapidly evolving field. In 2013, Pivotal proposed the concept of cloud native and has continued to interpret it. Below is Pivotal’s description of the characteristics of cloud-native architecture: 2015: 12-Factor, microservices-oriented, anti-fragile 2017: Observability, modularity, replaceability, disposability 2019: DevOps, continuous delivery, microservices, containers Many people’s first encounter with cloud native may have been through the CNCF.

Many cloud native open source components start with the service and add visualization later. Today I had a brainstorm and went the opposite way: first the visual interaction, then the underlying design. 1. One Canvas Covers Half of Cloud Native Users only need one canvas. Define the Workflow, and they can roam freely across all kinds of fancy Cloud Native applications.