DevOps & Cloud

Deployment, cloud, containers, CI/CD, monitoring, and infrastructure

skills in category: 20,326
pages available: 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 browser

Browse devops & cloud skills

Showing 7,825–7,848 of 20,326 skills

VerboseADrift is the divergence between declared infrastructure and live infrastructure. Naming its sources matters because they call for different remedies.devopsgobashVotes: 0GitHub stars: 2
MinimalAFind the gap between what your code says the infrastructure is and what it actually is — on a schedule, before an unrelated deploy discovers it for you.devopsgobashVotes: 0GitHub stars: 2
VerboseA**Server Logs:** ``` 2026-04-10 14:00:05 [ERROR] Connection pool exhausted (available: 0/350) 2026-04-10 14:00:07 [ERROR] Query timeout after 5000ms 2026-04-10 14:00:08 [ERROR] Database unavailable ```devopsdatabaseVotes: 0GitHub stars: 2
MinimalA``` 2:00 PM - [EVENT] Database connection pool becomes exhausted 2:02 PM - [DECISION] Restart database service 2:03 PM - [METRIC CHANGE] Error rate spikes to 100% 2:05 PM - [ALERT] Automated alert fires 2:06 PM - [HUMAN ACTION] On-call engineer acknowledges 2:08 PM - [ESCALATION] Incident commander paged 2:15 PM - [ROOT CAUSE] Identified connection leak in query 2:20 PM - [REMEDIATION] Deploy fix 2:25 PM - [RESOLUTION] Service restored, error rate drops ```devopsdatabaseVotes: 0GitHub stars: 2
VerboseAState is the map between your code and real resources. Everything else in Terraform is downstream of it being correct, shared, and singular.devopsgoshellVotes: 0GitHub stars: 2
VerboseAA goroutine is a lightweight thread the runtime multiplexes onto OS threads. Channels are the typed conduits goroutines use to pass values and, crucially, ownership of data. The guiding maxim is "don't communicate by sharing memory; share memory by communicating."devopsgotestingVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
VerboseAThe pitch is often "a central place to store features," which undersells it into sounding like a database with a marketing team. The actual justification is narrower and sharper: **training/serving skew**.devopspythonrustVotes: 0GitHub stars: 2
MinimalA```python from opentelemetry import trace, metrics from opentelemetry.exporter.jaeger.thrift import JaegerExporter from opentelemetry.sdk.trace import TracerProvider from opentelemetry.sdk.trace.export import BatchSpanProcessordevopspythonsqlVotes: 0GitHub stars: 2
VerboseADisaster recovery has exactly two quantitative inputs, and every architectural choice downstream is a consequence of them.devopsrustgoVotes: 0GitHub stars: 2
MinimalAMake "undo" a fast, boring, rehearsed operation — so shipping is cheap and a bad release costs minutes rather than an outage.devopsgobashVotes: 0GitHub stars: 2
VerboseAA git SHA pins the transformation. It says nothing about what went into it. Check out the commit that produced last quarter's model, rerun the pipeline, and the job reads the *current* tables — with three months of new rows, a corrected billing field, and a column that was backfilled in April. The output is different, and nothing under version control can tell you why.devopspythongoVotes: 0GitHub stars: 2
MinimalAMake any past result — a model, a report, a number in a board deck — regenerable months later, by pinning the data as rigorously as the code.devopspythongoVotes: 0GitHub stars: 2
VerboseAThe purpose of a postmortem is to change the system, and that only works if people tell you what actually happened. Blame destroys that input directly: an engineer who expects to be named for a mistake reports incidents later, describes them more cautiously, and omits the detail that would have explained the failure. The cost is not abstract — it shows up as longer detection times on the next incident.devopsgosqlVotes: 0GitHub stars: 2
MinimalATurn incidents, delivery friction, and retro complaints into tracked changes that measurably move a number — instead of into documents nobody reads twice.devopsgotestingVotes: 0GitHub stars: 2
VerboseDA container image is an attack surface you chose. Every binary in it is a tool available to whoever gets code execution — `curl` to stage a payload, `apt` to install one, a shell to run it interactively.devopspythongoVotes: 0GitHub stars: 2
VerboseAThe annual compliance scramble exists because controls are tested once, by hand, shortly before the auditor arrives. That model fails on its own terms: period-based reports and certifications ask whether the control operated *throughout* the window, and a test performed in week 50 says nothing about weeks 1 through 49.devopspythongoVotes: 0GitHub stars: 2
MinimalAMake controls prove themselves continuously — checked by code, evidenced by machines — instead of reconstructing a year of assurance in the four weeks before an audit.devopsgoexpressVotes: 0GitHub stars: 2
VerboseACompute, object storage, block storage, a managed relational database, a message queue, a load balancer, a CDN — every major provider has all of these, and they are close enough in capability that comparing them line by line is wasted effort. If your architecture only uses the commodity layer, the choice is dominated by price, region availability, and what your team already knows.devopsgosqlVotes: 0GitHub stars: 2
MinimalAChoose a primary cloud by comparing the primitives and managed services you will actually use, weighting your team's existing skills and data gravity far above any feature-count comparison.devopsgosqlVotes: 0GitHub stars: 2
VerboseAThere is no such thing as "the migration." An estate is a collection of applications, and each one gets an independent disposition. The industry-standard framing is the six R's, and the discipline is to inventory every workload and assign one — with a reason — rather than applying a single strategy to everything.devopsgorefactoringVotes: 0GitHub stars: 2
VerboseALeast privilege is easy to state and hard to hold: grant each identity only the permissions it needs to do its job, and nothing more. The reason it matters is not tidiness — it is **blast radius**. Every credential eventually leaks or is misused; the only question the design controls is how much damage the holder of a leaked credential can do. A role scoped to read one bucket is a minor incident when it leaks. A role with `*` is a company-ending one.devopsrustgoVotes: 0GitHub stars: 2
MinimalAGrant each identity the least authority it needs, from short-lived credentials, so that a single compromised identity cannot become a full breach.devopsrustgoVotes: 0GitHub stars: 2
VerboseAAlmost every cloud estate is over-provisioned. Instances are sized from a guess, a worst-case peak that never materializes, or a copy-pasted template, and then never revisited. The result is a fleet running at a fraction of its paid capacity. Right-sizing — matching provisioned resources to measured usage — is the lever with the most headroom, and it compounds with every other technique, so it comes first.devopsgokubernetesVotes: 0GitHub stars: 2
MinimalACut the cloud bill through the levers that actually move it — right-sizing, commitment discounts, storage tiering, killing idle resources, and controlling egress — not by micro-optimizing individual line items.devopsgokubernetesVotes: 0GitHub stars: 2