Batchmaker family · full operations Next
W-Make Batch · Next
The Next.js migration of the complete Batchmaker operations suite, retaining its Express/SQLite domain core.
- Responsibility
- Migration architecture, domain backend contract, and operational UI modernisation.
- Technology
- Next.js 16 · TypeScript · Node.js · Express · SQLite · Playwright
- Status
- Live · active Next migration
- Positioning
- The production migration: domain invariants remain in the backend while the new client takes over the operational interface step by step.
Situation
Situation
A production system cannot be modernised through a big-bang frontend switch. Bookings, roles and shift logic must remain stable.
The migration therefore introduces Next.js over the same domain core instead of copying production, stock and calculations into a new browser domain.
Decisions
Decisions
- 01
Express and SQLite remain the source for domain logic, authentication and data integrity.
- 02
The Next client uses an explicit API contract and adopts routes incrementally rather than creating a shadow domain.
- 03
Health, role and route checks make each migration step verifiable.
What you can inspect
A look at the application.
What you can inspect
The flow as a model.
01
Domain core
Backend, data model and booking invariants remain the shared source of truth.
02
Next client
Operational routes are introduced as a typed Next.js interface.
03
Verification
API, role and smoke checks secure the migration.
04
Operations
Container and domain form a clearly separated production variant.
What remains
What remains
A production migration succeeds when the new client makes the domain core visible without duplicating it.
batchmaker-next.w-make.com →30-min analysis · free