> For the complete documentation index, see [llms.txt](https://docs.arkannis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkannis.net/cloud/azure/courses/az900-course/cloud-models-and-cloud-types/the-serverless-model.md).

# The Serverless Model

**IaaS, PaaS, SaaS are not the only models that can be run in the Cloud**

## The Serverless Model

* There are still servers...
* You just don't ever have to deal with them
* Even less access to the servers than PaaS

{% hint style="info" %}
*PaaS Notes:*

* *Even with PaaS, you have to choose an App Service Plan*
* *Within PaaS, scaling is your responsibilit*
  {% endhint %}

**Serverless means not worrying about choosing the right plan** **Serverless means bit worrying about scaling** **Serverless means you might pay $0 if you don't use the service (since you are paying for execution)**

## Azure Serverless Offers:

* Compute:
  * Azure Functions
  * Serverless Kubernetes (Virtual Nodes w/ ACI)
* Database:
  * Azure SQL Database Serverless
  * Cosmos DB Serverless


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.arkannis.net/cloud/azure/courses/az900-course/cloud-models-and-cloud-types/the-serverless-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.