Problem
Restaurant staff needed a more reliable way to manage operational tasks, reporting, and internal workflows without depending on manual processes.
Production System2024 - PresentFeatured project
Original Pho Eatery System
Original Pho Eatery System supports daily restaurant operations through a staff-facing portal and API layer. The system combines Node.js/Express backend services, MongoDB persistence, JWT authentication, Next.js protected routes, and Dockerized deployment practices.
Full stack developer responsible for backend APIs, staff portal features, authentication, containerized deployment, production troubleshooting, and stakeholder-driven iteration.
- Type
- Production System
- Timeline
- 2024 - Present
- Stack
- Docker, Node.js, Express
Context and Role
The system was built for real production use, with iterative changes based on daily stakeholder feedback and operational needs.
Outcome
The system improved daily throughput, reduced manual reporting work by 40%, and gave the business a production platform for continuing operational improvements.
Technologies Used
Stack and implementation focus
DockerNode.jsExpressMongoDBNext.jsTypeScriptJWT Auth
Key Features
- Staff portal with protected Next.js routes and authenticated workflows.
- REST API services built with Node.js, Express, and MongoDB.
- Dockerized backend services for repeatable deployment and environment consistency.
- Automated reporting and task workflows that reduced manual work by 40%.
Challenges and Decisions
- Used JWT authentication to protect staff-only routes and backend resources.
- Containerized backend services to reduce environment drift between local and production deployments.
- Prioritized practical operational fixes by tracing issues across logs, networking, API behavior, and user reports.
Review Summary
What this project is meant to prove.
The work connects a real problem to implementation choices, ownership, and an outcome. The engineering signal is in the path from context to decision to result.