Backend & web applications
Restaurant Management · ASP.NET Core
A web back office for a restaurant’s daily operations: dishes, ingredients, staff, reservations, orders and sales, in one ASP.NET Core application.
- Individual project
- domains managed in one app
- 6
- with EF Core 9 and SQL Server
- .NET 8
01Starting point
Context & mission
The problem
A restaurant juggles recipes, ingredients, reservations, orders and sales every day. When this information lives in different places, calculation errors and omissions pile up.
The mission
Bring the restaurant’s operations into one secured web application, with a relational model that does the maths instead of people.
My role
Designed and built on my own.
02Execution
What I did
Six business domains
Full CRUD screens for dishes, ingredients, staff, reservations, orders and sales.
Modelled recipes
Many-to-many dishes ↔ ingredients relation, with a junction entity that stores the quantity each recipe needs.
Computed in the database
Line totals and sale amounts computed directly by SQL Server (computed columns): a single source of truth.
Security and evolution
Accounts handled by ASP.NET Core Identity; schema versioned with Entity Framework Core migrations.
03Design
Architecture
ASP.NET Core MVC: controllers handle requests, models carry the entities and data context, Razor views render the interface, Entity Framework Core connects everything to SQL Server.
- Browser
- ControllersASP.NET Core MVC
- ModelsEntities · context
- EF Core 9Migrations
- SQL ServerComputed columns
- Razor viewsBootstrap · jQuery
- IdentityAccounts
04Impact
Results
- The restaurant’s operations brought into one secured application.
- Recipes and amounts that the database computes and keeps consistent.
05Wrap-up
Takeaways
What this project provesThe same modelling discipline, carried over to C# and .NET: I move between ecosystems without starting over.
06Technology
Full stack
- C#
- .NET 8
- ASP.NET Core MVC
- Razor
- EF Core 9
- SQL Server
- ASP.NET Core Identity
- Bootstrap
- jQuery