https://github.com/interviewandhealth/microservices-backend-fastapi-base
Base for the FastAPI Microservice Architecture Backend for the Mock Interview and Mental Health Platform
https://github.com/interviewandhealth/microservices-backend-fastapi-base
base fastapi microservice template
Last synced: 7 months ago
JSON representation
Base for the FastAPI Microservice Architecture Backend for the Mock Interview and Mental Health Platform
- Host: GitHub
- URL: https://github.com/interviewandhealth/microservices-backend-fastapi-base
- Owner: InterviewAndHealth
- Created: 2024-09-27T10:26:23.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-01-12T17:21:58.000Z (about 1 year ago)
- Last Synced: 2025-01-25T14:44:07.947Z (about 1 year ago)
- Topics: base, fastapi, microservice, template
- Language: Python
- Homepage:
- Size: 11.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Microservices FastAPI Backend Base
### This repository will be used as the base for the microservice architecture backend for the mock interview project.
## Architecture
- `app`: Responsible for handling the FastAPI application.
- `database`: Responsible for handling the database operations.
- `models`: Responsible for handling the database models.
- `repository`: Responsible for handling the database operations for a specific entity.
- `services`: Responsible for handling the business logic.
- `routes`: Responsible for handling the API routes.
- `utils`: Responsible for handling the utility functions.
- `types`: Responsible for handling the type definitions for request and response payloads and broker messages.
- `dependencies.py`: Responsible for handling the dependencies and middlewares.
### Broker
In the `services` directory, there is a `broker` directory that is responsible for handling the communication between the services. The broker is divided into two parts:
- `events`: Responsible for handling the events between the services.
- `rpc`: Responsible for handling the Remote Procedure Calls (RPC) between the services.