How gonza-10/api-restaurante works
This repository is a restaurant-management REST API. Its documented workflow is a client request routed through Django REST Framework viewsets, serialized and validated against restaurant entities, then persisted in SQL Server. The README identifies CRUD for products, categories, tables, employees and orders; it describes reservations, payments, cash management, role permissions and suggestions as modeled but not yet exposed. A separate browser/HTTP-server demo handles products in temporary memory. Some route and model internals are unsampled, so the graph limits those links to documented responsibilities.
Main entry points: views.py Viewsets · models.py Restaurant Models · settings.py Django Settings · urls.py API Routes
Components 16
REST API
- API Routes
restaurante/urls.py - Viewsets
restaurante/views.py - Serializers
restaurante/serializers.py - Error Handler
restaurante/exception_handler.py - Django Settings
config/settings.py
Restaurant Domain
- Restaurant Models
restaurante/models.py - Menu Items
restaurante/models.py - Tables
restaurante/models.py - Employees
restaurante/models.py - Orders
restaurante/models.py - Planned Domains
restaurante/models.py
Persistence
- SQL Server
Product Demo
- Demo Browser
app.js - Demo HTTP Server
SERV_WEB.py - Temporary Products
SERV_WEB.py
Other components
- API Client
Connections 10
- API Client → API Routes: sends requests
- API Routes → Viewsets: routes to
- Viewsets → Serializers: uses
- Viewsets → Restaurant Models: queries
- Serializers → Restaurant Models: validates and saves
- Django Settings → Error Handler: configures
- Django Settings → SQL Server: configures connection
- Restaurant Models → SQL Server: persists via ORM
- Demo Browser → Demo HTTP Server: fetches products
- Demo HTTP Server → Temporary Products: reads and writes