Project Overview#
Project: Portfolio
Semester: DAT 3rd Semester 2026
Focus: Production-ready Java backend with workflow and resource optimization for a modern canteen kitchen.
MiseOS is built around one core idea: the kitchen should have the same digital discipline as physical mise en place.
The system supports the full journey from dish suggestion to published menu, including ingredient requests, allergen visibility, and multilingual communication for guests.
Vision#
MiseOS is a kitchen operations backend that helps teams move from fragmented, manual planning to a structured, role-based workflow.
It supports:
- creative ownership for line cooks
- editorial and operational control for head/sous chef
- reliable publication of guest-facing menu information
Problem Statement#
In many kitchens, menu planning still depends on handwritten notes, Word files, and verbal coordination.
This creates recurring problems:
- dish ideas are scattered across stations
- ingredient needs are difficult to consolidate
- translation and allergen communication are error-prone
- management lacks one coherent overview
MiseOS solves this by centralizing planning, approvals, menu publishing, and ingredient workflows in one backend system.
Business Logic: The Creative Canteen#
The application models a kitchen where quality comes from station-level ownership and management curation.
1) Section-based planning (bottom-up)#
Instead of top-down menu creation, stations submit proposals independently.
- Stations: Hot, Cold/Starter, Salad, Bakery/Dessert
- Line cooks submit weekly dish suggestions per station
- Empty slots are allowed intentionally
- Suggestions can later be translated for guest-facing use
2) Head chef curation and verification#
The head/sous chef has full overview and editorial authority.
- Review and approve/reject/edit suggestions
- Assemble complete weekly menu
- Balance variety and operational feasibility
- Ensure Danish/English guest content quality
3) Ingredient and ordering flow#
Ingredient needs are linked directly to operational planning.
- Cooks submit ingredient requests
- Management reviews and approves
- Requests are aggregated into shopping lists
- Finalized list supports better ordering decisions
4) Nice-to-have extension (waste reduction)#
A planned extension is takeaway handling for leftovers:
- Enable surplus portions after lunch
- Allow guest/customer reservation flow
- Track offered/sold/remaining portions
Architecture#
MiseOS is implemented as a layered backend architecture separating HTTP handling, business logic, and persistence.
The system consists of:
- Javalin controllers handling REST and WebSocket communication
- Service layer implementing domain logic and workflow rules
- DAO layer using JPA/Hibernate for database access
- PostgreSQL relational data model
- JWT authentication and role-based authorization
- External API integrations for AI, translation, and weather data
Development Log (Portfolio Posts)#
The project development is documented weekly in the blog series.
- Why I’m Building MiseOS
- Understanding the Kitchen: From Real World to User Stories
- From ERD to JPA: Design decisions and Hibernate implementation
- Integrating AI & Translation: External APIs and Service Layer Design
- Designing and Implementing the Service Layer
- Wiring the Application: Controllers, Routes, and Server Configuration
- Testing the API Layer and Real-Time Notifications with WebSockets
- From Fake IDs to Secure Passports: A Journey into JWT Middleware
- From Localhost to Live: Deploying MiseOS with CI/CD
- Writing the map, while building the city: A Week on MiseOS API Documentation
API Documentation#
All resource endpoints, request/response examples, and authentication details are documented in the API documentation.
Project Video#
A short walkthrough of the MiseOS portfolio and backend system.
The video covers the project overview, development log, API documentation, and a live backend demo in IntelliJ.
Source Code#
The complete Java backend implementation is available on GitHub.