29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
|
---
|
||
|
|
title: "Python developer's introduction to designing an API and choosing your framework(s)"
|
||
|
|
date: 2024-06-30T09:00:00-07:00
|
||
|
|
draft: true
|
||
|
|
tags:
|
||
|
|
- "django"
|
||
|
|
- "FastAPI"
|
||
|
|
---
|
||
|
|
|
||
|
|
This article is written for anyone currently evaluating how to choose an API Framework (FastAPI, django-ninja etc.) and wondering how to setup a project from scratch, using SQLAlchemy or Django for ORM.
|
||
|
|
|
||
|
|
We're focusing on choice and preferences. The objective is to make something that's confusing/annoying/energy-draining feel more comfortable and go from frozen 🥶 to cruising 🚄.
|
||
|
|
|
||
|
|
Ingredients:
|
||
|
|
|
||
|
|
* Open up your own design doc/enhancement proposal and start writing
|
||
|
|
* The method
|
||
|
|
* Some components for evaluation
|
||
|
|
* tl;dr Conclusion
|
||
|
|
|
||
|
|
One of the reasons why it's good to have this approach, is that most ORMs and API frameworks can be decoupled. But it's good to narrow down your search from the beginning. If you already have a strong preference for SQLAlchemy or Django, you should be comfortable with that choice.
|
||
|
|
|
||
|
|
## The method
|
||
|
|
|
||
|
|
At the beginning, you should probably wonder about what criteria are important
|
||
|
|
|
||
|
|
## Th
|
||
|
|
|
||
|
|
## More resources
|