Food Out is a food delivery application, written using Micro-service approach and primarily Go programming language.
Coming soon...
The task is to implement whole food delivery application with micro-service architecture and Go programming language.
- Account management;
- Auth;
- Managing restaurant info and its menu.
- Managing working status for couriers.
- Serving shop.
- Creating orders.
- Functionality to accept or reject orders for restaurants and couriers.
Account Service is responsible for managing user accounts.
It provides CRUD operations on the account resource.
Auth service is responsible for user sessions, it uses Redis for storing these sessions.
Client Service is an entrance to the system for clients. It handles clients requests and generates events for the rest of the system.
It stores client-related information, f.e. addresses, in PostgreSQL.
Restaurant Service handles restaurant's requests and generates events for the system.
It stores the restaurant specific information in PostgreSQL.
Courier service handles the courier related requests.
It stores the courier related information in PostgreSQL.
Menu service is responsible for managing restaurant's menus. It uses PostgreSQL for storing this information.
This service handles three domain fields, which are:
- Shop Viewing(makes a selection of categories and dishes for particular restaurant and (optional) category).
- Menu Management Service(handles CRUD operations for restaurant's dishes and categories).
- Order Content Validation(validates a set of dishes, that was required by user and generates an event of complete Order).
Shop Viewer is exposed, but the Menu Management Service and Order Content Validation Service are not, they are private for this system.
Order service is responsible for managing orders in the system.
Order service contains two domain fields:
- Order Viewer Service, which provides an interface to query orders by the participants(clients, couriers, restaurants).
- Order Management Service, which is responsible for perfoming Create,Update,Remove operations on the dishes and categories.
The OrderViewer is exposed, but the Order Management Service is private for the system and does not have public API.
Image Uploader is a utillity-service that handles media uploading/receiving, it is primarily used as an image storage for dishes, categories, restaurants, user profiles.
Most of the services are using PostgreSQL for storing information.
Auth service is using Redis for storing sessions, due to it's great functionality of automatically deleting objects.
For storing media(images) MinIO is used.
Kafka is used as a message broker.