Home

HAP is a tool for quick design and development of enterprise software. It requires no code and can be mastered and used by ordinary business people. With flexible functional components, personalized systems such as CRM, ERP, OA, and project management can be built for managing corporate activities like production, sales, procurement, etc. HAP Server is the container deployment edition of HAP SaaS service, which empowers enterprise users to build no-code application platform on their own cloud computing facilities.

Design

HAP is based on microservice architecture and uses Docker mirrors for deployment. In the private deployment mode, in order to ensure the stability of the system while facilitating deployment, HAP adopts a monolithic program model based on the microservice architecture, merging each independent microservice mirror into one big mirror (microservice application mirror). The configuration files are completely built-in, but can be overwritten and extended. The mirror also contains relevant data storage components (available by default in standalone deployment mode), such as MySQL, MongoDB, Redis, Elasticsearch, Kafka, file object storage based on MinIO and online file preview module based on OnlyOffice. You can eventually start HAP service with a single command.

The monolithic program mode is inseparable from the single point of failure, but the monolithic mode of the HAP Server is more for simplifying deployment, and the internal is still a collection of microservices (similar to the multi-container Pod in Kubernetes), so in order to ensure the availability of each service process within the container, a health check thread is preset in the container, which allows automatic recovery when a service fails. Standalone Deployment Mode

Cluster Deployment Mode is a more granular clustering of microservices and dependent components, including clusters of storage components (like MySQL, MongoDB, Redis, Elasticsearch, Kafka, etc.) and clusters of microservice applications. Microservice application mirrors themselves are already adaptive to standalone and cluster deployment modes. Cluster Deployment Mode

Iteration

HAP Server and HAP SaaS Edition are basically the same in terms of functionality, while the SaaS Edition iterates more frequently, and it generally takes about 2 to 3 weeks to synchronize the features to the HAP Server, which is because it takes some time for edition merging, testing, bug fixing, etc. All of this is also to ensure the stability of the new edition of the Private Deployment.