/fastapi_architecture_template

FastAPI based on the construction of the front and back of the separation of rights control system, using a unique pseudo three-tier architecture model design, and as a template library free open source

Primary LanguagePythonMIT LicenseMIT

FastAPI Best Architecture

GitHub Static Badge

English | 简体中文

FastAPI framework based on the front-end and back-end separation of the middle and back-end solutions, follow the pseudo three-tier architecture design, support for python3.10 and above versions

Its purpose is to allow you to use it directly as the infrastructure of your new project, this repository as a template library open to any person or enterprise can be used for free!

Continuously updated and maintained

Pseudo three-tier architecture

The mvc architecture is a common design pattern in python web, but the three-tier architecture is even more fascinating.

In python web development, there is no common standard for the concept of three-tier architecture, so we'll call it a pseudo three-tier architecture here

workflow java fastapi_best_architecture
view controller api
data transmit dto schema
business logic service + impl service
data access dao / mapper crud
model model / entity model

Online preview

Unfortunately, we don't have the funds to provide an online preview, you can deploy by checking out local-development, or directly using Docker to deploy, or at fastapi_best_architecture_ui See a preview of some of the screenshots

Features

  • Design with FastAPI PEP 593 Annotated Parameters
  • Global asynchronous design with async/await + asgiref
  • Follows Restful API specification
  • Global SQLAlchemy 2.0 syntax
  • Casbin RBAC access control model
  • Celery asynchronous tasks
  • JWT middleware whitelist authentication
  • Global customizable time zone time
  • Docker / Docker-compose deployment
  • Pytest Unit Testing

TODO:

  1. Pydantic 2.0

Built-in features

  1. User management: system user role management, permission assignment
  2. Department Management: Configure the system organization (company, department, group...)
  3. Menu Management: Configuration of system menus, user menus, button privilege identification
  4. Role Management: Assign role menu privileges, assign role routing privileges
  5. Dictionary Management: Maintain common fixed data or parameters within the system.
  6. Operation Logs: logging and querying of normal and abnormal system operations.
  7. Login Authentication: graphical authentication code background authentication login
  8. Login Logs: Logging and querying of normal and abnormal user logins
  9. Service Monitoring: server hardware device information and status
  10. Timed Tasks: online task control (modify, delete, pause...)
  11. Interface Documentation: Automatically generate online interactive API interface documentation.

TODO:

  1. Dynamic Configuration: Dynamic configuration of the system environment (site title, logo, filing, footer...)
  2. code generation: according to the table structure, visualize the generation of additions, deletions, modifications and checks of the business code.
  3. File Upload: Docking cloud OSS and local backup.
  4. System Notification: proactively send timed task notifications, resource warnings, service anomaly warnings...

Local development

  • Python: 3.10+
  • Mysql: 8.0+
  • Redis: The latest stable version is recommended
  • Nodejs: 14.0+

BackEnd

  1. Install dependencies

    pip install -r requirements.txt
  2. Create a database fba, choose utf8mb4 encoding

  3. Install and start Redis

  4. Create a .env file in the backend/app/ directory

    cd backend/app/
    touch .env
  5. Copy .env.example to .env

    cp .env.example .env
  6. Database migration alembic

    cd backend/app/
    
    # Generate migration file
    alembic revision --autogenerate
    
    # Execute the migration
    alembic upgrade head
  7. Start celery worker and beat

    celery -A tasks worker --loglevel=INFO
    # Optional, if you don't need to use the scheduled task
    celery -A tasks beat --loglevel=INFO
  8. Modify the configuration file as needed

  9. Execute the backend/app/main.py file to start the service

  10. Browser access: http://127.0.0.1:8000/api/v1/docs


Front

Click fastapi_best_architecture_ui for details

Docker deploy

Warning

Default port conflict:8000,3306,6379,5672

As a best practice, shut down on-premises services before deployment:mysql,redis,rabbitmq...

  1. Go to the directory where the docker-compose.yml file is located and create the environment variable file .env

    cd deploy/docker-compose/
    
    cp .env.server ../../backend/app/.env
    
    # This command is optional
    cp .env.docker .env
  2. Modify the configuration file as needed

  3. Execute the one-click boot command

    docker-compose up -d --build
  4. Wait for the command to complete automatically

  5. Visit the browser: http://127.0.0.1:8000/api/v1/docs

Test data

Initialize the test data using the backend/sql/init_test_data.sql file

Development process

For reference only

BackEnd

  1. Define the database model (model) and remember to perform database migration for each change
  2. Define the data validation model (schema)
  3. Define routes (router) and views (api)
  4. Define the business logic (service)
  5. Write database operations (crud)

Front

Click fastapi_best_architecture_ui for details

Test

Execute unittests via pytest

  1. Create the test database fba_test, select utf8mb4 encoding

  2. Using backend/sql/create_tables.sql file to create database tables

  3. Initialize the test data using the backend/sql/init_pytest_data.sql file

  4. Enter the app directory

    cd backend/app/
  5. Execute the test command

    pytest -vs --disable-warnings

Contributors

Special thanks

Sponsor us

If this program has helped you, you can sponsor us with some coffee beans ☕

WeChat Alipay 0x40D5e2304b452256afD9CE2d3d5531dc8d293138
WeChat Pay Ali Pay ERC20

License

This project is licensed under the terms of the MIT license