How a Full‑Stack Charging‑Station Project Can Boost Your Interview Portfolio

Project Overview

The author led the backend development of a charging‑station platform from scratch, collaborating with a front‑end specialist. The system supports ordinary users, VIP users, investors, operators, and administrators, offering functions like registration, authentication, payment, coupon management, real‑time charging, and analytics.

Core Process and User‑Side Features

Key user flows include investor onboarding, site construction, user registration (including invitation codes), login via password, SMS, or WeChat, binding bank cards, initiating charging sessions, applying coupons, and ending charging. The user interface comprises pages for home, site details, site map, charging start, charging in progress, personal center, recharge, coupons, points, and orders.

Backend Service Modules

The backend is split into multiple Maven modules, each serving a specific domain:

charge-common-service : unified job scheduling, gateway, OAuth, and system logging.

charge-common : core utilities and pure‑tool libraries.

charge-market : marketing services, common utilities, job scheduling, API DTOs, and message consumers.

charge-user : user services, common utilities, job scheduling, API DTOs, and message consumers.

charge-station : site platform services, common utilities, job scheduling, API DTOs, hardware integration core, and message consumers.

charge-pay : payment services, job scheduling, message consumers, and API DTOs.

Software Architecture Stack

The system is built on Spring Cloud, Spring Boot, MySQL, MyBatis, Redis, RabbitMQ, XXL‑job, Nacos, Seata, Hystrix, Sentinel, OpenFeign, EMQX (MQTT), and a Vue 3 + Element Plus + Vant front‑end. Additional tools include Spring Security, MyBatisGenerator, Hutool, and InfluxDB for time‑series data.

Project Highlights

Practical implementation of distributed locks.

Solutions for message loss and duplicate consumption.

Cache consistency and cache‑penetration protection.

Idempotency handling.

Custom Spring Boot starters.

Distributed transaction management.

Sharding (database and table) strategies.

Extensive use of AOP and custom annotations.

Unified parameter validation, logging, and exception handling.

Multi‑level caching and rate limiting.

Asynchronous processing and flash‑sale (seckill) functionality.

Design Documentation

To date, 35 design documents have been produced, covering topics such as coupon expiration handling, real‑time charging data, email sending, internal messaging, Elasticsearch‑based dashboards, project deployment, Netty integration, multi‑data‑source configuration, ThreadLocal usage, SMS verification, system logging, and detailed schema design for each business domain.

Key Takeaways

The article demonstrates how a comprehensive, production‑grade charging‑station system can be architected and implemented, offering concrete code modules, architectural diagrams, and design rationales that interviewees can discuss to demonstrate deep technical competence.