* Veritabanı bağlantılarını paylaşmak.
* Güvenlik, authentication, rol gereksinimleri vb. kuralları zorunlu kılmak.
* Ve daha birçok şey...

Tüm bunları, kod tekrarını minimumda tutarak yaparsınız.

## İlk Adımlar { #first-steps }

Çok basit bir örneğe bakalım. Şimdilik o kadar basit olacak ki pek işe yaramayacak.

Ama bu sayede **Dependency Injection** sisteminin nasıl çalıştığına odaklanabiliriz.

	user.Age = 20
	if err := DB.Create(&user).Error; err != nil {
		t.Errorf("failed to create user, got error %v", err)
	}

	var user2 User
	DB.First(&user2, user.ID)
	user2.Age = 30
	time.Sleep(time.Second)
	if err := DB.Clauses(clause.OnConflict{UpdateAll: true}).Create(&user2).Error; err != nil {
		t.Fatalf("failed to onconflict create user, got error %v", err)
	} else {
		var user3 User
		DB.First(&user3, user.ID)

    assertThat(server.takeRequest().exchangeIndex).isEqualTo(0)

    // Give the server time to enact the socket policy if it's one that could happen after the
    // client has received the response.
    Thread.sleep(500)
    val response2 = getResponse(newRequest("/b"))
    response1.body
      .source()
      .timeout()
      .timeout(100, TimeUnit.MILLISECONDS)

    }
}

fun BuildType.killProcessStep(
    mode: KillProcessMode,
    os: Os,
    arch: Arch = Arch.AMD64,
    executionMode: BuildStep.ExecutionMode = BuildStep.ExecutionMode.DEFAULT,
) {
    steps {
        killProcessStep(this@killProcessStep, mode, os, arch, executionMode)
    }
}

fun String.toCapitalized() = this.replaceFirstChar { if (it.isLowerCase()) it.titlecase(Locale.getDefault()) else it.toString() }

      }

      OverrideParam.ReadTimeout -> {
        client =
          client
            .newBuilder()
            .socketFactory(
              DelayingSocketFactory(onRead = {
                Thread.sleep(100L)
              }),
            ).build()

        overrideBadImplementation(override = override.override, testItFails = testItFails)
      }

      OverrideParam.ConnectTimeout -> {
        client =

    // Service b startup takes at least 353 millis, but starting the timer is delayed by at least
    // 150 milliseconds. so in a perfect world the timing would be 353-150=203ms, but since either
    // of our sleep calls can be arbitrarily delayed we should just assert that there is a time
    // recorded.
    assertThat(startupTimes.get(b)).isNotNull();
  }

  public void testServiceStartStop() {

Je vous en dirai plus sur les images de conteneurs, Docker, Kubernetes, etc. dans un chapitre à venir : [FastAPI dans des conteneurs - Docker](docker.md).

///

## Étapes préalables avant de démarrer { #previous-steps-before-starting }

Il existe de nombreux cas où vous souhaitez effectuer certaines étapes **avant de démarrer** votre application.

Par exemple, vous pourriez vouloir exécuter des **migrations de base de données**.

							</div>
						</div>
						<div id="progressIndicator" class="progress-indicator d-none" role="status" aria-live="polite">
							<div class="progress-steps">
								<div class="progress-step" data-phase="intent">
									<div class="step-icon"><i class="fa fa-lightbulb-o" aria-hidden="true"></i></div>

3. **Reliability**: 
   - Persistent handles survive 99% of network interruptions
   - Witness protocol achieves <5 second failover time
4. **Compatibility**: Works with Windows Server 2016+ and Azure Files

## Next Steps

1. **Immediate Actions**:
   - Set up Windows Server test environment
   - Create detailed technical specifications for Phase 1
   - Identify and evaluate Java RDMA libraries

2. **Phase 1 Kickoff**:

import javax.inject.Inject;

import static java.util.Comparator.naturalOrder;
import static java.util.stream.Collectors.toList;
import static java.util.stream.Collectors.toSet;

/**
 * Orchestrates the steps required to generate or update various release notes files.
 */
public class GenerateReleaseNotesTask extends DefaultTask {
    private static final Logger LOGGER = Logging.getLogger(GenerateReleaseNotesTask.class);