[Open Source] A SpringBoot Low-Code Development Platform with Comprehensive Documentation and Multi-Data-Source Support
![[Open Source] A SpringBoot Low-Code Development Platform with Comprehensive Documentation and Multi-Data-Source Support](https://yy123.ink/api/img/1782596033508-7dewf9.jpg)
1. Project Overview
oh-boot is a SpringBoot low-code development platform built with SpringBoot 3.0, SpringSecurity 6.0, Mybatis-Plus, Kafka, and other frameworks. It features comprehensive documentation and comments and supports multiple data sources.
2. Open Source License
Licensed under MIT
3. Screenshots
Effect picture










4. Feature Overview
A SpringBoot low-code development platform with multiple data source support, built using SpringBoot 3.0, SpringSecurity 6.0, Mybatis-Plus, Kafka, and other frameworks.
-
It adopts a component-based architecture to extend different business functionalities, making it easy to implement various business requirements. Simply import the required components as needed.
-
Provides generic APIs and supports API-level authorization for connected clients. Integrates Kafka to support asynchronous MQ APIs and handle massive request volumes.
-
Supports independent schema and database initialization for each database (please disable the relevant initialization after it is completed).
-
Supports multiple data sources. Different data sources can be selected through frontend parameters or backend configuration, allowing data from different business domains to be stored separately.
-
The frontend integrates bpmn.js and uses the Camunda workflow engine, making workflow design simple.
-
Supports code generation, scheduled tasks, file storage, SMS integration, and more.
5. Tech Stack
oh-boot is a SpringBoot low-code development platform built with SpringBoot 3.0, SpringSecurity 6.0, Mybatis-Plus, Kafka, and other frameworks. It features comprehensive documentation and comments and supports multiple data sources.
You can quickly and easily set up a development environment using oh-parent and oh-framework. For example, if you need to separate the basic system management features into an independent project, simply combine oh-parent, oh-framework, and oh-system into a standalone project. You can also divide the backend into different service projects based on business requirements and server resources. Refer to the system management project oh-sys.