Professional project · Controle Sistemas
AstroDelivery
I developed AstroDelivery as the sole developer at Controle Sistemas. I handled requirements, architecture, interfaces, services and documentation. Decisions and deliverables were validated by the company supervisor.
- Context
- Professional project · Controle Sistemas
- My role
- Sole fullstack developer
- My contribution
- Responsible for requirements, architecture, frontend, backend and documentation, with validation by the company supervisor.
One product, different journeys
Customers need to discover products, configure orders and follow fulfillment. Restaurants need a coherent way to manage menus, orders and integrations.
I built the storefront with Next.js/React and the services with Node.js/TypeScript, Express and Prisma. PostgreSQL, Redis and RabbitMQ support data and communication flows.
Decision: orders must preserve their rules
Flavors, sizes, add-ons, bundles and promotions make a catalog more complex than a price list. The server calculates authoritative amounts; the interface presents selections and the order summary.
Order history preserves order details, while states represent fulfillment stages. This supports understanding what was ordered even after catalog changes.
Decision: separate fulfillment from asynchronous reactions
I separated business responsibilities and used event communication for reactions such as notifications. The interface follows order updates through SSE.
Payment and external integrations require distinguishing requests, confirmations and state updates. Documentation records these flows and their limits; the architecture does not imply guaranteed delivery of every event.
Contribution and evidence
My responsibility covered requirements, modeling, implementation and documentation, with business validation by the Controle supervisor. The code belongs to the professional context and remains private.
The public landing page presents the product and its user journeys. The image in this case study is a capture of that public presentation page.
Delivery and limits
The result is a platform connecting the customer journey to restaurant operations through a configurable catalog, orders and integrations.
External integrations depend on their respective providers. Each restaurant operates in its own configuration context; the landing page provides the public product presentation.