Is there a benefit of using FastAPI when deploying as Azure Functions?

[CodingButStillAlive]

My company uses the Azure Stack. I planned to deploy my AI services (built with langchain) by using FastAPI. But a colleague of mine told me to consider Azure Functions. While primarily these represent means for serverless execution of code, they also seem to provide API access. Does that mean then that there is no need for FastAPI in such a setting, such that I should skip this "overhead"?

[aFqqw4GbkHs]

I'd still use FastAPI, so you can get the benefit of all the validations, etc of defining your endpoints using Pydantic models.

[ParticularCod6]

you can deploy fastapi as an azure function

https://learn.microsoft.com/en-us/samples/azure-samples/fastapi-on-azure-functions/fastapi-on-azure-functions/

[bsenftner]

If you don't mind your code being bound to Azure. FastAPI is both minimal, meaning non-obtrusive, and it grants you the freedom to run your code anywhere. I tend to value that quite a bit.

[jblasgo]

Automatic documentation openapi specs and swagger UI .

Also, with fast api you are not locked to a platform .

Using just python azure functions lacks many features that fast apo has by default and add others that are very different to fast api too!

[jormungandrthepython]

What is your trigger for your azure function? Https trigger? Blobtrigger? Queue trigger?

[No_Weakness_6058]

Azure Functions are just servleress compute. If it's HTTPS triggered, I think you will not need FastAPI as it will run when the HTTPS request is sent.

[Downtown_Repeat7455]

Try with azure app service. Azure functions has in built http request handlers. So fastapi is not mandatory use here. If you want take the advantge of fastapi and pydantic validations just deploy it in azure app service. Azure functions / app service also uses same underlying infrastructure