How ffcfelps1/projeto_semestral_entrega_via_drones works
SkySwift is a web application for autonomous-drone delivery management. A customer browses the site, can sign in, creates and confirms a delivery request, and follows its status and history; a separate tracking view calculates a route. The frontend also exposes pricing, help, sales contact, and notifications. Backend microservices handle identity, orders, routing, email, and notifications, with an event bus distributing service events. The tree also contains serverless API dispatchers for several services. The README documents their role, but their runtime wiring beyond sampled dispatchers is not fully visible.
Main entry points: App.jsx App shell · pedidos.js Order service · barramento_eventos/server.js Event bus · notificacoes/server.js Notification service
Components 30
Web experience
- App shell
front/src/App.jsx - Order pages
front/src/PedidoPage.jsx - Order state
front/src/usePedidos.js - Order client
front/src/pedidosEntregaService.js - Drone tracking
front/src/DroneTrackingSection.jsx - Account pages
front/src/AccountPage.jsx - Login page
front/src/LoginPage.jsx - Notifications page
front/src/NotificacoesPage.jsx - Pricing page
front/src/PrecosPage.jsx - Help center
front/src/SuportePage.jsx - Notification client
front/src/notificacoesService.js
Delivery operations
- Order service
back/gestao_de_pedidos/routes/pedidos.js - Order database
back/gestao_de_pedidos/database.js
Platform services
- User service
back/cadastro_usuario/server.js - Route service
back/entrega_via_drone/server.js - Email service
back/contato_email/server.js - Notification service
back/notificacoes/server.js - Event bus
back/barramento_eventos/server.js - Service runtime
back/shared/runtime.js
Serverless APIs
- Order API router
api/gestao_de_pedidos/handler.js - Order API rules
api/gestao_de_pedidos/_utils.js - User API router
api/cadastro_usuario/handler.js - User API helpers
api/cadastro_usuario/_utils.js - Email API
api/contato_email/handler.js - Route API
api/entrega_via_drone/handler.js - Event API
api/barramento_eventos/handler.js - Notifications API
api/notificacoes/handler.js
Other components
- Customer
- Routing provider
- MySQL
Connections 37
- Customer → App shell: uses
README.md - App shell → Order pages: renders
front/src/App.jsx - Order pages → Order state: uses
front/src/PedidoPage.jsx - Order state → Order client: calls
front/src/usePedidos.js - Order client → Order service: requests
README.md - App shell → Drone tracking: renders
front/src/App.jsx - App shell → Login page: renders
front/src/App.jsx - App shell → Account pages: renders
front/src/App.jsx - App shell → Pricing page: routes
README.md - App shell → Help center: routes
README.md - App shell → Notifications page: routes
front/src/App.jsx - App shell → Notification client: calls
front/src/App.jsx - Notification client → Notification service: requests
README.md - App shell → User service: requests
front/src/App.jsx - App shell → Email service: requests
front/src/App.jsx - Order service → Order database: reads/writes
back/gestao_de_pedidos/routes/pedidos.js - Order service → MySQL: persists
- Order API router → Order API rules: uses
api/gestao_de_pedidos/handler.js - User API router → User API helpers: uses
api/cadastro_usuario/handler.js - Route service → Routing provider: requests route
back/entrega_via_drone/server.js - Route service → Event bus: publishes route event
back/entrega_via_drone/server.js - Order service → Event bus: publishes order events
README.md - Event bus → Order service: delivers events
README.md - Event bus → Notification service: delivers events
README.md - Notification service → MySQL: persists
README.md - User service → MySQL: reads/writes
README.md - Order API router → Order service: alternative deployment
README.md - User API router → User service: alternative deployment
README.md - Email API → Email service: alternative deployment
README.md - Route API → Route service: alternative deployment
README.md - Event API → Event bus: alternative deployment
README.md - Notifications API → Notification service: alternative deployment
README.md - User service → Service runtime: uses lifecycle
back/cadastro_usuario/server.js - Route service → Service runtime: uses lifecycle
back/entrega_via_drone/server.js - Event bus → Service runtime: uses lifecycle
back/barramento_eventos/server.js - Notification service → Service runtime: uses lifecycle
back/notificacoes/server.js - Order service → Event bus: updates order status
README.md