They tend to require more complex configurations, a message/job queue manager, like RabbitMQ or Redis, but they allow you to run background tasks in multiple processes, and especially, in multiple servers.

        assertNull(result);
    }

    // Test convertBooleanQuery with null queryBuilder from processor
    @Test
    public void test_convertBooleanQuery_withNullQueryBuilder() {
        // Create processor that returns null
        QueryProcessor nullProcessor = new QueryProcessor() {
            @Override

 *
 * <ul>
 *   <li>An annotation named just "Suppress" might someday be treated by a non-Android tool as a
 *       suppression. This would follow the precedent of many of our annotation processors, which
 *       look for any annotation named, e.g., "GwtIncompatible," regardless of package.
 *   <li>An annotation named just "Suppress" might suggest to users that the test is suppressed

E também depois que a `response` é gerada, antes de retorná-la.

Por exemplo, você pode adicionar um cabeçalho personalizado `X-Process-Time` contendo o tempo em segundos que levou para processar a solicitação e gerar uma resposta:

{* ../../docs_src/middleware/tutorial001_py310.py hl[10,12:13] *}

/// tip | Dica

with JMH as of 2021-04-30.

The async profiler is neat because it does not suffer from the safepoint
bias problem. And because it makes pretty flame graphs!

Let user processes read performance stuff:
```
sudo bash
echo 0 > /proc/sys/kernel/kptr_restrict
echo 1 > /proc/sys/kernel/perf_event_paranoid
exit
```

It is made up of 3 architecture modules:

- **core-runtime**: Provides the runtimes or "containers" in which code runs. These runtimes include the Gradle client, the daemon and the worker processes. This is the base module on which all other architecture modules depend.
- **core-configuration**: Allows the build structure and work, such as tasks, to be specified. This includes the project model, the DSL and so on.

     *
     * <p>The returned list should not contain duplicate repositories (based on their
     * equality) or null entries, as these will cause validation failures when the
     * request is processed.
     *
     * @return the list of remote repositories to use, or {@code null} to use session defaults
     * @see Session#getRemoteRepositories()
     */
    @Nullable
    List<RemoteRepository> getRepositories();

These examples run the server program (e.g Uvicorn), starting **a single process**, listening on all the IPs (`0.0.0.0`) on a predefined port (e.g. `80`).

This is the basic idea. But you will probably want to take care of some additional things, like:

* Security - HTTPS
* Running on startup
* Restarts
* Replication (the number of processes running)
* Memory
* Previous steps before starting

          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "build-cache-example-client",
          "build-process-services",
          "configuration-cache-base",
          "files",
          "internal-instrumentation-processor",
          "kotlin-dsl-plugins",
          "kotlin-dsl-provider-plugins",
          "language-native",
          "testing-jvm-infrastructure",

Das bedeutet, dass anstelle des normalen Prozesses, bei dem Ihre Benutzer Requests an Ihre API senden, **Ihre API** (oder Ihre App) **Requests an deren System** (an deren API, deren App) senden könnte.