HC Community Property Management System – Backend Architecture Overview

The HC Community Property Management System, launched by the java110 team in April 2017, is an open‑source, front‑end/back‑end separated, distributed Java project that includes backend, frontend, owner‑mobile, and property‑mobile modules, with detailed development tools, hardware/software requirements, microservice structure, and deployment instructions.

Selected Java Interview Questions
Selected Java Interview Questions
Selected Java Interview Questions
HC Community Property Management System – Backend Architecture Overview

Introduction: The HC Community Property Management System is an open‑source project initiated by the java110 team in April 2017, featuring a front‑end/back‑end separated, distributed architecture with backend, frontend, owner mobile, and property mobile modules.

System Requirements

Development Tools

Java 1.8, IntelliJ IDEA/Eclipse, MySQL, Redis.

Hardware Requirements

Test environment: 4 CPUs, 16 GB RAM, 80 GB disk.

Software Requirements

Install MySQL 5.6, Zookeeper, Redis, and Kafka. Start services: service-eureka, service-api, service-order, service-community, service-store, service-user, service-front, service-fee, service-common, and service-job.

Project Structure

java110-bean      # stores entity beans, VO, DTO, PO objects
java110-config   # system configuration classes, logback.xml, etc.
java110-core     # core classes, micro‑service interfaces, context, factories, events
java110-db       # SQL mapper files
java110-generator # code generator
java110-service  # base service classes and dynamic SQL engine
java110-util     # utility classes (time, logging, constants, exception handling)
service-api      # unified external API
service-comment  # comment service
service-common   # common services (FTP upload, workflow, device info)
service-community# community assets (buildings, units, houses, inspections, notifications, parking, repairs, visitors)
service-eureka   # service registry
service-fee      # fee processing (items, payment, refunds)
service-front    # external access (login, permission, WeChat, app integration)
service-job      # scheduled tasks (face sync, employee sync, fee billing)
service-log      # system logging
service-order    # transaction consistency and business tracing
service-report   # reporting
service-rule     # business rules
service-sequence # ID generation using Google Snowflake
service-store    # merchant services (property, agents, developers, operators)
service-user     # user, owner, family member information

System Functions

A diagram of system functions is provided in the original material.

Running Effect

Access the application via http://localhost:3000/. Use username wuxw and password admin to log in, as shown in the screenshots.

Source Code Access

Scan the QR code of the “Java知音” public account and reply “智慧社区” to obtain the download link.

Microservicesdistributed architecturebackend developmentOpen-sourceProperty Management
Selected Java Interview Questions
Written by

Selected Java Interview Questions

A professional Java tech channel sharing common knowledge to help developers fill gaps. Follow us!

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.