In the previous chapter about HTTPS we learned about how HTTPS provides encryption for your API. These concepts also apply to any other type of web API. In the next chapters, I'll give you more concrete recipes to deploy FastAPI applications.īut for now, let's check these important conceptual ideas. I'll tell you a bit more about these concepts here, and that would hopefully give you the intuition you would need to decide how to deploy your API in very different environments, possibly even in future ones that don't exist yet.īy considering these concepts, you will be able to evaluate and design the best way to deploy your own APIs. In the end, the ultimate objective is to be able to serve your API clients in a way that is secure, to avoid disruptions, and to use the compute resources (for example remote servers/virtual machines) as efficiently as possible. We'll see how they would affect deployments. Replication (the number of processes running).
When deploying a FastAPI application, or actually, any type of web API, there are several concepts that you probably care about, and using them you can find the most appropriate way to deploy your application. OAuth2 with Password (and hashing), Bearer with JWT tokensĬustom Response - HTML, Stream, File, othersĮxamples of Replication Tools and StrategiesĪlternatives, Inspiration and Comparisons
Dependencies in path operation decorators
0 kommentar(er)
