But in many cases, you will want to run several worker processes at the same time.

### Multiple Processes - Workers { #multiple-processes-workers }

### 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.

	}

	keys := store.List()
	if len(keys) != 6 {
		// 1 multiple + 5 single PUTs
		t.Fatalf("expected len(keys)=6, but found %d", len(keys))
	}

	var resultItems []TestItem
	for _, key := range keys {
		if key.ItemCount > 1 {
			items, err := store.GetMultiple(key)
			if err != nil {
				t.Fatalf("unable to get multiple items; %v", err)
			}
			resultItems = append(resultItems, items...)

    }

    /**
     * Benchmark that tests multiple property configurations in a single operation.
     * This simulates a more realistic scenario where multiple properties are set on a bean.
     */
    @Benchmark
    public void benchmarkOriginalHelperMultipleProperties() throws Exception {
        RealisticTestBean bean = new RealisticTestBean();

        // Set multiple properties in one benchmark iteration

## Query parameter list / multiple values { #query-parameter-list-multiple-values }

When you define a query parameter explicitly with `Query` you can also declare it to receive a list of values, or said in another way, to receive multiple values.

For example, to declare a query parameter `q` that can appear multiple times in the URL, you can write:

<div class="screenshot">
<img src="/img/tutorial/sql-databases/image01.png">
</div>

## Update the App with Multiple Models { #update-the-app-with-multiple-models }

Now let's **refactor** this app a bit to increase **security** and **versatility**.

    }

    // We need to take in multiple lifecycles
    @Test
    public void testCalculationOfBuildPlanWithMultipleExecutionsOfModello() throws Exception {
        File pom = getProject("project-with-multiple-executions");
        MavenSession session = createMavenSession(pom);
        assertEquals(
                "project-with-multiple-executions", session.getCurrentProject().getArtifactId());

	AssertAssociationCount(t, &user, "Pets", 1, "after Set Update with multiple associations")
	AssertAssociationCount(t, &user, "Toys", 1, "after Set Update with multiple associations")
}

// Test Set + Update with multiple associations using real database
func TestClauseAssociationSetUpdateWithMultipleAssociations(t *testing.T) {
	ctx := context.Background()

> NOTE: Server side replication is supported for idempotent versions on directory objects.

* Keep commits discrete. Avoid including multiple unrelated changes in a single commit.
* Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation.

### Testing changes

After making changes, you can test your code in 2 ways:

#### Run tests