A multi-stage build is a Docker technique where you use one image for building your app and another smaller image for running it. Why we do multi-stage build, because the .NET SDK image is big but has all the build tools. The .NET Runtime image is small and optimized for production. You copy only the published output from the build stage into the runtime stage.
```dockerfile
@ -94,6 +98,8 @@ I'll explain what these Docker file commands;
Even if your app runs behind a reverse proxy like Nginx, Cloudflare or a load balancer, always enforce HTTPS. Why? Because internal traffic can still be captured if you don't use SSL and also cookies, HSTS, browser APIs require HTTPS. In .NET, you can easily enforce HTTPS like this:
@ -181,6 +187,8 @@ options.Cookie.SameSite = SameSiteMode.Strict; // or Lax
The **JIT (Just-In-Time) compiler** converts your app’s Intermediate Language (IL) into native CPU instructions when the code runs. _Tiered JIT_ means the runtime uses 2 stages of compilation. Actually this setting is enabled by default in modern .NET. So just keep it on.
@ -207,6 +215,8 @@ In .NET 8+, you don’t have to manually enable PGO (Profile-Guided Optimization
When we break up with our lover, we often argue and regret it later. When an application breaks up with an operating system, it should be done well 😘 ...
When your app stops, maybe you deploy a new version or Kubernetes restarts a pod... the OS sends a signal called `SIGTERM` (terminate).
A **graceful shutdown** means handling that signal properly, finishing what’s running, cleaning up, and exiting cleanly (like an adult)!
@ -227,10 +237,20 @@ On K8s, set `terminationGracePeriodSeconds` and wire **readiness**/startup probe
## 11) Load Test
Sometimes arguing with our lover is good. We can see her/his face before marrying 😀 Use **k6** or **bombardier** and test with realistic payloads and prod-like limits. Don't be surprise later when your app is running on prod! Test these topics:
Sometimes arguing with our lover is good. We can see her/his face before marrying 😀 Use **k6** or **bombardier** and test with realistic payloads and prod-like limits. Don't be surprise later when your app is running on prod! These topics should be tested: `CPU %` , `Time in GC` , `LOH Allocations` , `ThreadPool Queue Length` and `Socket Exhaustion`.
### About K6
- A modern load testing tool, using Go and JavaScript.
- 29K stars on GitHub
- GitHub address: https://github.com/grafana/k6
### About Bombardier
- Fast cross-platform HTTP benchmarking tool written in Go.
Ebicoglu
12 months ago
