A single HTTP call may require follow-up requests to be made to handle authentication challenges, redirects, and HTTP-layer timeouts. In such cases multiple connections, requests, and responses may be attempted. Follow-ups are another reason a single call may trigger multiple events of the same type.

### One Load Balancer - Multiple Worker Containers { #one-load-balancer-multiple-worker-containers }

When working with **Kubernetes** or similar distributed container management systems, using their internal networking mechanisms would allow the single **load balancer** that is listening on the main **port** to transmit communication (requests) to possibly **multiple containers** running your app.

///

## Multiple middleware execution order { #multiple-middleware-execution-order }

## Overview

MinIO implements an S3 extension to perform multiple concurrent fan-out upload operations. A perfect use case scenario for performing fan-out operations of incoming TSB (Time Shift Buffer's). TSBs are a method of facilitating time-shifted playback of television signaling, and media content.

With any of the methods above it would look like this in the `/docs`:

<img src="/img/tutorial/body-fields/image01.png">

### `Body` with multiple `examples` { #body-with-multiple-examples }

You can of course also pass multiple `examples`:

{* ../../docs_src/schema_extra_example/tutorial004_an_py310.py hl[23:38] *}

The client (browser) will know that the response comes from the correct server because it is using the cryptography they agreed using the **HTTPS certificate** before.

### Multiple Applications { #multiple-applications }

In the same server (or servers), there could be **multiple applications**, for example, other API programs or a database.

        new SecureRandom().nextBytes(secondFileId);

        // When - set file ID multiple times
        assertDoesNotThrow(() -> {
            request.setFileId(firstFileId);
            request.setFileId(secondFileId);
            request.setFileId(testFileId);
        }, "Should handle multiple setFileId calls");
    }

    @Test
    @DisplayName("Should test interface with anonymous implementation")

	<fieldset class="mb-3">
		<legend><la:message key="labels.index_lang" /></legend>
		<label for="langSearchOption"><la:message key="labels.index_lang" /></label>
		<la:select property="lang" styleId="langSearchOption" multiple="true"
			styleClass="form-control">
			<c:forEach var="item" items="${langItems}">
				<la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
			</c:forEach>
		</la:select>
	</fieldset>

	<fieldset class="mb-3">
		<legend><la:message key="labels.index_lang" /></legend>
		<label for="langSearchOption"><la:message key="labels.index_lang" /></label>
		<la:select property="lang" styleId="langSearchOption" multiple="true"
			styleClass="form-control">
			<c:forEach var="item" items="${langItems}">
				<la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
			</c:forEach>
		</la:select>
	</fieldset>

or any other case variation (uppercase, first letter in uppercase, etc), your function will see the parameter `short` with a `bool` value of `True`. Otherwise as `False`.


## Multiple path and query parameters { #multiple-path-and-query-parameters }

You can declare multiple path parameters and query parameters at the same time, **FastAPI** knows which is which.

And you don't have to declare them in any specific order.