Admin boundary notes
sky-take-out reads like a campus meal ordering backend, but the useful lesson is boundary control. Staff, dishes, set meals, and shop status belong to the admin side, while cart, address book, checkout, and order tracking belong to users.
A loose CRUD split makes order status, payment confirmation, and dashboard counts hard to trust.
Order flow checks
My current pass keeps the role split visible. The order module owns state transitions, payment callbacks only confirm and compensate, and statistics read from one clear order source.
Java, Spring Boot, MyBatis, MySQL, Redis, and JWT all have a place here, but each tool should support the business line instead of hiding it.
What I would polish next
The next useful cleanup is a stricter order-state table plus tests for cancel, pay, deliver, and refund edges. That would make the backend safer to explain and extend.