How bitisanop/cryptoexchange_tradingplatform_coinexchange works
Project type and purpose
• This is a full-stack, Java-based, microservice architecture for a digital asset exchange and perpetual contract trading system (“BITISAN”).
• It uses Spring Cloud (Feign clients, gateway), Spring Boot, MyBatis, Redis, RocketMQ, Netty, MySQL/MongoDB, with separate front-end (Vue/H5/Admin) modules.
File structure
• Top-level modules (Maven multi-module):
• bitisan-api: interface definitions (Java packages with Feign clients, DTOs, entities)
• bitisan-gateway: API Gateway (Spring Cloud Gateway/Zuul)
• bitisan-service: many sub-services (admin, user, exchange, market, match, coinswap, earn, option, swap, second, p2p, udun, permission, robot-market, robot-normal, open)
• bitisan-netty: custom Netty server for real-time/Push logic (WebSockets, Shiro, handlers)
• bitisan-generate: code generator for MyBatisPlus
• bitisan-web: front-end resources (Vue, H5, Admin UI)
• bitisan-util: common/shared libraries and dependency management
• config/bootstrap.yml: common Spring Cloud Config (centralized configuration)
• Notice each service has its own controller, service, mapper, entity, MQ listeners, xxl-job tasks, and resources.
README insights
• Core function: multi-asset trading (spot, contract, options, swap, second market, P2P).
• Uses Redis for caching & locks, RocketMQ for event-driven order processing, MySQL for core data, MongoDB for market data.
• Front-ends: SPA (Vue), H5 (uniApp), Native mobile (Swift, Java Android), Admin console.