hs-web/hsweb-framework

hsweb (haʊs wɛb) 是一个基于spring-boot 2.x开发 ,首个使用全响应式编程的企业级后台管理系统基础项目。

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 7th, 2026
Created on January 18th, 2016
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 3,017
Total Stargazers: 8,396 (+0)
Total Subscribers: 694 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,236 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • 帮助 (15)
  • 需求 (5)
  • bug (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

hsweb is a Spring Boot 2.x-based enterprise backend management framework that implements fully reactive programming throughout its stack.

The framework addresses the need for a modern, scalable backend system by building entirely on reactive technologies. It uses R2DBC for reactive database access, Project Reactor for reactive streams, and Spring WebFlux for reactive web handling. This end-to-end reactive approach eliminates blocking operations across the entire application layer. The framework provides reactive CRUD operations through an ORM abstraction, reactive transaction control, and reactive permission management with support for RBAC and data-level access control.

Developers should adopt this framework if they are building new backend systems and have familiarity with Project Reactor and Spring Boot fundamentals. It suits modular, extensible backend architectures where reactive performance characteristics matter. The project recommends consuming it as Maven dependencies rather than forking and modifying directly, allowing teams to select only the modules they need. The framework includes built-in support for user management, permission assignment, data dictionaries, and static file uploads, reducing boilerplate for common administrative features.

Development activity shows consistent module organization with clear separation of concerns across authorization, datasource management, logging, and system functionality. The project maintains comprehensive README documentation at the module level to guide adoption of individual components. The framework explicitly acknowledges its reactive-first design as a core architectural decision, with non-reactive support marked as a future consideration rather than a current priority.