Our Design Idea

Enterprise Application Cloud Operating System

For enterprise IT, enterprise applications are the most important manifestation of the value of enterprise IT. However, no matter whether it is developing applications or using applications, it is necessary to face the lowest level of computing resources (IaaS/virtualization/physical server), leading to the technology stack. It’s very long and needs to do a lot of work that is not directly related to the business, such as: development and operation environment construction; server management; network management; delivery process management; technical architecture support; basic technical service provision; technical tool maintenance and other operations and technical work. These tasks are universal to all enterprise applications. If these tasks are packaged and automated, the enterprise can focus on its own business, so that the efficiency of enterprise IT can be greatly improved.

Kato packages the above repetitive tasks in an application-centric way, and supports the development, architecture, delivery and operation and maintenance of enterprise applications. This abstract granularity can not only simplify the management of enterprise applications, but also meet business needs. Flexibility. When docking the underlying infrastructure, through the software definition implementation and docking, various types of infrastructure can be docked. Through the above design, an operating system for enterprise applications is naturally formed.

Non-invasive Architecture

Kato takes broad support for enterprise applications as its primary goal. Broad support for enterprise applications means that various enterprise applications can be developed, structured, and operated on Kato. This is also a key point that affects the user experience. In order to achieve this goal, Kato adopts Non-invasive architecture. The “non-intrusive” architecture is simple to use, and existing applications can be supported without modification.

Specifically start from three aspects:

  • In the development stage, docking with the code repository, automatically identifying development language type, without changing developer habits, as far as possible without modifying the existing code, directly compiling, building and run.

  • In the architecture stage, if the existing system does not have a distributed architecture, Kato provides the Service Mesh architecture, and the business module can become a microservice architecture without changing the code.

  • In the operation and maintenance stage, it is difficult to find the original developers for the old legacy system, and it is difficult to migrate to the new operating environment. Kato uses the method of dynamically generating configuration files and network relationships to migrate and run the legacy system. Operation and maintenance and governance functions are provided by Kato in the form of “non-intrusive” plug-ins, which can be loaded according to functional needs.

The “non-intrusive” architecture also shows that there is no binding to the user, and the developed application can be developed and run without Kato.

Application-centric, Connecting Enterprise Applications and Enterprise Computing Resources

“Application-centric” is the core design concept of Kato, and it is also the abstract idea of ​​Kato, emphasizing attention to business, exposing business-related technical concepts to the outside, and unified packaging of technical concepts not directly related to business. By abstracting in this way, users don’t need to think too much about the server, which is the Serverless architecture.

Through the application-centric abstraction, enterprise applications can be decoupled from enterprise computing resources. The lifecycle management of enterprise applications is not directly related to computing resources, which means that the development of enterprise applications can be developed on any type of computing resources. Enterprise applications can be directly installed and run on any type of computing resource, and can be migrated from one resource to another at any time.

Computing resources are completely transparent to users, and computing resources are connected according to different usage scenarios. When computing resources are connected to public resources, it is public cloud. When computing resources are connected to private resources, it is private cloud. When computing resources are connected at the same time Connecting public and private resources is the hybrid cloud.

Kato realizes the connection of enterprise applications and enterprise computing resources through decoupling, and the accumulation of various enterprise applications that are docked forms an enterprise application market, and the accumulation of various enterprise computing resources that are docked form an enterprise computing resource market, applications in the application market and resources in the resource market Can be combined freely. The process of combined use is manifested in two interactive interfaces, SaaS and PaaS. SaaS realizes click-to-use without knowing technology, and PaaS realizes advanced customized development.