How exrick/xmall works
Project type and purpose
• XMall is a SOA-style, distributed e-commerce platform. It comprises several loosely coupled services (content, order, member, search, SSO, management) communicating via Dubbo (RPC) with ZooKeeper as service registry. It provides a Vue-based public storefront, a classic SpringMVC back-office UI, and multiple backend services exposing interfaces for business logic and persistence.
File structure
• Top-level modules (in xmall-parent):
• generatorSqlmapCustom – MyBatis code generator tool
• xmall-common – shared annotations, constants, utils, Redis clients
• xmall-content (interface & service) – content/advertisement service
• xmall-manager (interface, DAO, POJO, service, web) – back-office administration
• xmall-front-web – SpringMVC façade for the public front end
• xmall-search (interface & service) – Elasticsearch-based product search
• xmall-sso (interface & service) – single sign-on/auth service
• xmall-parent – parent POM
• xmall-search, xmall-sso, xmall-manager, xmall-content, xmall-common – typical multi-module Maven layout
• Each service module has DAO, service-impl, interface, MyBatis XML, and Spring XML (DAO, service, transaction, Redis, ActiveMQ configs). Web modules include SpringMVC configs, controllers, views/static assets.
README for additional insights
• XMall runs as six independent deployable units (content, manager-service, manager-web, front-web, search-service, sso-service).
• Uses: Spring, SpringMVC, MyBatis, Dubbo, ZooKeeper, MySQL/Mycat, Redis, Elasticsearch, ActiveMQ, Shiro, Swagger2, Docker, Nginx, third-party SDKs (Qiniu, weather API).
• Describes service responsibilities: content/banner management, user/permission management, order processing, search indexing, SSO.
Detail without overcomplicating
• Six services, two web modules, shared libraries, and infrastructure
• Cross-cutting concerns (common module) only if it clarifies reuse
• Keep labels concise; group similar services if needed