From c2c4d1651ffc1424b236a817503132621bb641ff Mon Sep 17 00:00:00 2001 From: Yerassyl Zhanymkanov Date: Sat, 8 Jun 2024 13:04:26 +0200 Subject: [PATCH] Fix the missing Dispatch link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1f35b48..4a65200 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ There are many ways to structure a project, but the best structure is one that i Many example projects and tutorials divide the project by file type (e.g., crud, routers, models), which works well for microservices or projects with fewer scopes. However, this approach didn't fit our monolith with many domains and modules. -The structure I found more scalable and evolvable for these cases is inspired by Netflix's Dispatch, with some minor modifications. +The structure I found more scalable and evolvable for these cases is inspired by Netflix's [Dispatch](https://github.com/Netflix/dispatch), with some minor modifications. ``` fastapi-project ├── alembic/