All categories
DevOps & Cloud
Deployment, cloud, containers, CI/CD, monitoring, and infrastructure
- 20,326
- 847
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse devops & cloud skills
Showing 7,849–7,872 of 20,326 skills
- VerboseThe choice is not about scale or sophistication. It is about whether the model's inputs can change between the moment you would precompute and the moment the prediction is used.Votes: 0GitHub stars: 2
- VerboseEvery autoscaling decision is driven by one of three trigger types, and mature systems layer them rather than choosing one.Votes: 0GitHub stars: 2
- MinimalMatch capacity to demand automatically, on a signal that actually tracks load, without flapping or starving requests during the ramp.Votes: 0GitHub stars: 2
- VerboseAn ADR records one decision at the moment it is made, with the information that was actually available. Its value is not the decision — that is visible in the code — but the *forces*: what was considered, what was rejected, and what the choice costs. Six months later the code shows what; only the ADR shows why.Votes: 0GitHub stars: 2
- MinimalRecord the structure of a system and the reasoning behind it, so that the next engineer can change it without re-deriving every decision from scratch.Votes: 0GitHub stars: 2
- VerboseVersioning exists because you cannot deploy your clients. Once a third party — or your own mobile app sitting in an app store review queue — depends on a response shape, that shape is a contract, and the only safe assumption is that some caller depends on every observable detail of it.Votes: 0GitHub stars: 2
- VerboseTLS is either configured deliberately or inherited from a distro default written years ago. Pin the protocol floor and let 1.3 negotiate its own suites.Votes: 0GitHub stars: 2
- Slo Sli Definition**SLO (Service Level Objective):** What we promise (99.9%)Votes: 0GitHub stars: 2
- Serverless ArchitectureServerless is a billing-and-scaling model, not a badge of modernity.Votes: 0GitHub stars: 2
- Multi Cloud Strategy\"Multi-cloud\" is a loose word that hides four distinct architectures withVotes: 0GitHub stars: 2
- Model MonitoringThe layers trade timeliness against definitiveness.Votes: 0GitHub stars: 2
- Mlops Pipeline DesignSoftware CI assumes a git sha plus a lockfile determines the build.Votes: 0GitHub stars: 2
- Ml DeploymentA model in production is never just weights.Votes: 0GitHub stars: 2
- Message Queue SelectionMessaging systems fall into three fundamental shapes, and most bad choices comeVotes: 0GitHub stars: 2
- Kubernetes Resource ManagementTwo numbers with two different audiences.Votes: 0GitHub stars: 2
- Incident Timeline Creation**Server Logs:**Votes: 0GitHub stars: 2
- Iac Best PracticesState is the map between your code and real resources.Votes: 0GitHub stars: 2
- Feature Store DesignThe pitch is often \"a central place to store features,\" which undersells it intoVotes: 0GitHub stars: 2
- Disaster Recovery PlanningDisaster recovery has exactly two quantitative inputs, and every architecturalVotes: 0GitHub stars: 2
- Data Versioning ReproducibilityA git SHA pins the transformation.Votes: 0GitHub stars: 2
- Continuous ImprovementThe purpose of a postmortem is to change the system, and that only works if peopleVotes: 0GitHub stars: 2
- Container Security HardeningA container image is an attack surface you chose.Votes: 0GitHub stars: 2
- Compliance AutomationThe annual compliance scramble exists because controls are tested once, byVotes: 0GitHub stars: 2
- Cloud Provider TradeoffsCompute, object storage, block storage, a managed relational database, a messageVotes: 0GitHub stars: 2