Scenarios
Complete programs for jobs that come up again and again. Each scenario explains the approach, shows the code (compiled with the library in CI), and lists what to change for production. Copy them as a starting point.
| Scenario | What it shows |
|---|---|
| A deployment script | Upload a release with resume, unpack it, switch a symlink atomically, restart, health-check through the connection, roll back. |
| A fleet health check | Check many hosts in parallel, each with its own connection and time limit, and report every host. |
| A file sync job | Mirror a local directory to a server: only changed files, atomic replacement, safe to rerun after a failure. |
| A database through a jump host | Reach a database inside a private network through a bastion, from any ADO.NET provider. |
| A background worker | A hosted service that fetches files on a schedule over a shared, reconnecting connection. |
The samples are runnable projects: an ssh-like command-line tool, an
ASP.NET Core API, and a worker service.