How floriaaan/goodfood works
Project type and purpose
• This is a full-stack, microservices-based food-ordering platform (“GoodFood 2.0”) with:
• Mobile client (Expo React Native, TypeScript)
• Web client (Next.js, TypeScript)
• API Gateway (Go) exposing HTTP/REST to clients
• ~12 domain services (Node.js/TypeScript, Go, C#/.NET) communicating via gRPC and an event broker
• Each service owns its own datastore (PostgreSQL or Redis)
• Infrastructure as code (Terraform), container orchestration (Docker Compose, Kubernetes), CI/CD (GitHub Actions)
File structure
• Top-level “apps/” folders contain frontends:
• apps/web: Next.js app with pages, components, hooks
• apps/mobile: Expo app with screens, components, native hooks
• “services/” contains one folder per microservice: gateway, user, basket, payment, product, restaurant, promotion, order, delivery, stock, notification, log, reporting
• Each service has src/handlers, lib (AMQP, proxy, ORM), middleware, server entrypoint, proto/.
• Prisma ORM for Node.js services, native Go or C# clients for others.
• Dockerfile, local Docker Compose, Kubernetes manifests under services/…/k8s, Terraform under services/…/terraform.
• “services/proto” defines the shared gRPC interfaces.
• CI/CD: .github/workflows/* for each service pipeline.
• Infrastructure provisioning in top-level terraform/ and kubernetes/ folder.
Read the README for insights
• A table lists each microservice’s port, language, and database.
• Instructions cover Terraform backend setup, Docker Compose, Kubernetes on Kind, and per-service README references.
• Microservices expose gRPC and some expose HTTP (gateway, webhook endpoints).