System Services — service layer
Backend microservices grouped by business domain. Messaging, approval, tickets, alerts, contracts, and reports serve every app.
Six domains
Microservices grouped by domain, deployed and scaled on their own
Energy operations
PV-storage-charging microgrid
Charging operations
Energy storage operations
Solar operations
Energy EMS
Virtual power plant
Load aggregation
Power trading support
Zero-carbon scenes
Zero-carbon buildings
Zero-carbon parks
Zero-carbon homes
Zero-carbon government offices
Public-institution energy-carbon
Zero-carbon associations
Zero-carbon MICE
Zero-carbon campuses
Zero-carbon community
Zero-carbon transport
Zero-carbon hospitals
Smart buildings
Smart lighting
Smart street lighting
Smart HVAC
Smart parking
Parking and charging network management
Smart water saving
Carbon management
ESG & sustainability
Carbon assets
Inclusive carbon
Product carbon footprint
Building LCA
GHG inventory
Carbon factor library
Tariff data
Zero-carbon factory
Zero-carbon mine
Zero-carbon water
Zero-carbon targets
Charging supervision
Energy-carbon supervision
Green supply chain
Supplier portal
MeetCarbon Green Finance
Enterprise management
Human resources
Customer relationships
MeetCarbon Academy
Project management
Asset sharing
Procurement & warehouse
Administration
Finance management
Enterprise core
Customer service
Platform foundation
Smart one-card
IoT device management
Data access hub
Smart O&M
Digital twin
Interconnection interface management
Investment evaluation
Six shared platform services
Messaging · approval · tickets · alerts · contracts · reports — shared infrastructure for every app
Message center
In-app, email, SMS, and WeCom channels
Approval center
Visual workflows with mobile approval
Work orders
Alert → ticket → resolution → close
Alert management
Multi-source ingest, four-level classification, linked handling
Contract center
Full-type life cycle with AI recognition
Report engine
Multi-dimension analysis, multi-format export
Microservice design principles
Independent deploy
Each service compiles, deploys, and scales on its own
Independent schema
Each service owns its own database schema
Service discovery
Nginx gateway routes and load-balances traffic
Graceful fallback
A single-service failure does not take others down