In den nächsten Kapiteln werde ich Ihnen mehr **konkrete Rezepte** für das Deployment von FastAPI-Anwendungen geben.

Aber schauen wir uns zunächst einmal diese grundlegenden **konzeptionellen Ideen** an. Diese Konzepte gelten auch für jede andere Art von Web-API. 💡

## Sicherheit – HTTPS { #security-https }

        <abbr title="2023-08-26">at the time of writing this</abbr>
        »»»

    Result (German):

        «««
        <abbr title="auch bekannt als: Endpunkte, Routen">Pfad</abbr>
        <abbr title="Programm das auf Fehler im Code prüft">Linter</abbr>
        <abbr title="Konvertieren des Strings eines HTTP-Requests in Python-Daten">Parsen</abbr>

#### Bei anderen Cloudanbietern deployen { #deploy-to-other-cloud-providers }

FastAPI ist Open Source und basiert auf Standards. Sie können FastAPI-Apps bei jedem Cloudanbieter Ihrer Wahl deployen.

Folgen Sie den Anleitungen Ihres Cloudanbieters, um FastAPI-Apps dort bereitzustellen. 🤓

## Performanz { #performance }

github.com/charmbracelet/x/ansi v0.8.0/go.mod h1:wdYl/ONOLHLIVmQaxbIYEC/cRKOQyjTkowiI4blgS9Q=
github.com/charmbracelet/x/exp/golden v0.0.0-20240815200342-61de596daa2b h1:MnAMdlwSltxJyULnrYbkZpp4k58Co7Tah3ciKhSNo0Q=
github.com/charmbracelet/x/exp/golden v0.0.0-20240815200342-61de596daa2b/go.mod h1:wDlXFlCrmJ8J+swcL/MnGUuYnqgQdW9rhSD61oNMb6U=
github.com/charmbracelet/x/term v0.2.1 h1:AQeHeLZ1OqSXhrAWpYUtZyX1T3zVxfpZuEQMIQaGIAQ=

?n!.&re&ganampsi,h.togrof,?sih.togrof,???em?irp?orhc?w??n!goloc?i&lno!.&egats-oree,llecpael,oree,redliubetisbew,ysrab,??w??o!.e&civres,tisbew,?hp?latipac?tse&gdirb?rif??z!.&amil,tikcats,???ruoblem??om?p!.&bog?gro?lim?mo&c?n??ten?ude??irg?yks??r!.&bilten,moc?nac,ossa??a&c!htlaeh??pmoc?wtfos??bc?eh?if?ots!.&e&rawpohs,saberots,?y&flles,srab,???taeht?u&ces?sni?t&inruf?necca??za???s!.&a!disnim321,?b!ibnal?rofmok??c!a??d!b?n&arb?ubroflanummok???e?f?g!ro??h!f??i!trap??k!shf??l?m!oc,t??n!mygskurbrutan??...

"hem", "heu", "hi ", "ho", "i", "igual", "iguals", "ja", "l'hi", "la", "les", "li", "li'n", "llavors", "m'he", "ma", "mal", "malgrat", "mateix", "mateixa", "mateixes", "mateixos", "me", "mentre", "més", "meu", "meus", "meva", "meves", "molt", "molta", "moltes", "molts", "mon", "mons", "n'he", "n'hi", "ne", "ni", "no", "nogensmenys", "només", "nosaltres", "nostra", "nostre", "nostres", "o", "oh", "oi", "on", "pas", "pel", "pels", "per", "però", "perquè", "poc ", "poca", "pocs", "poques", "potser", "propi",...

"hem", "heu", "hi ", "ho", "i", "igual", "iguals", "ja", "l'hi", "la", "les", "li", "li'n", "llavors", "m'he", "ma", "mal", "malgrat", "mateix", "mateixa", "mateixes", "mateixos", "me", "mentre", "més", "meu", "meus", "meva", "meves", "molt", "molta", "moltes", "molts", "mon", "mons", "n'he", "n'hi", "ne", "ni", "no", "nogensmenys", "només", "nosaltres", "nostra", "nostre", "nostres", "o", "oh", "oi", "on", "pas", "pel", "pels", "per", "però", "perquè", "poc ", "poca", "pocs", "poques", "potser", "propi",...

        for all the RNG in Keras. We plan to switch on the new code path by
        default in tf 2.8, and the behavior change will likely to cause some
        breakage on user side (eg if the test is checking against some golden
        number). These 3 APIs will allow user to disable and switch back to
        legacy behavior if they prefer. In future (eg TF 2.10), we expect to

honefoss.no
hongo.hiroshima.jp
honjo.akita.jp
honjo.saitama.jp
honjyo.akita.jp
hoplix.shop
hopto.me
hopto.org
hornindal.no
horokanai.hokkaido.jp
horonobe.hokkaido.jp
horse
horten.no
hosp.uk
hospital
host
hostedpi.com
hosting
hosting-cluster.nl
hostyhosting.io
hot
hotel.hu
hotel.lk
hotel.tz
hotels
hotelwithflight.com
hotmail
house

honefoss.no
hongo.hiroshima.jp
honjo.akita.jp
honjo.saitama.jp
honjyo.akita.jp
hoplix.shop
hopto.me
hopto.org
hornindal.no
horokanai.hokkaido.jp
horonobe.hokkaido.jp
horse
horten.no
hosp.uk
hospital
host
hostedpi.com
hosting
hosting-cluster.nl
hostyhosting.io
hot
hotel.hu
hotel.lk
hotel.tz
hotels
hotelwithflight.com
hotmail
house