Computer Β· Part C - Software, Algorithms and Computation Β· Major topic 14 of 39
Version Control, Collaboration, DevOps, SRE and Platform Engineering
Coordinating people and code, automating delivery, keeping systems dependable and reducing the distance between idea and safe production operation.
170 items insideCOM-14
Also look at: Science & Technology: Computer Architecture, Operating Systems, Programming and Software Systems
- 1
Historical evolution β key dates
- Source-control systems help teams coordinate evolving code.1970s-1980s
- Centralized version-control systems and automated build systems spread.1990s
- Git is created for distributed version control.2005
- Continuous integration, infrastructure automation, containers and DevOps practices gain adoption.2000s-2010s
- Site reliability engineering, cloud-native orchestration and platform teams become established practices.2010s
- GitOps, software supply-chain security, internal developer platforms and AI-assisted operations expand.2020s
- 2
Version control foundations
- Repository; working tree; staging/index; commit; branch; tag; remote; diff; merge; rebase; conflict; history
12 more points
- Repository
- Working tree
- Staging/index
- Commit
- Branch
- Tag
- Remote
- Diff
- Merge
- Rebase
- Conflict
- History
- Centralized vs distributed version control; Git mental model; ignore rules; hooks; large-file storage; submodules
6 more points
- Centralized vs distributed version control
- Git mental model
- Ignore rules
- Hooks
- Large-file storage
- Submodules
- Branching strategies; trunk-based development; release branches; signed commits/tags; protected branches
5 more points
- Branching strategies
- Trunk-based development
- Release branches
- Signed commits/tags
- Protected branches
- Repository; working tree; staging/index; commit; branch; tag; remote; diff; merge; rebase; conflict; history
- 3
Team collaboration
- Issue tracker; task board; pull/merge request; review checklist; code ownership; labels; milestones; release note
8 more points
- Issue tracker
- Task board
- Pull/merge request
- Review checklist
- Code ownership
- Labels
- Milestones
- Release note
- Collaboration etiquette; review latency; conflict negotiation; documentation; decision records; handover
6 more points
- Collaboration etiquette
- Review latency
- Conflict negotiation
- Documentation
- Decision records
- Handover
- Issue tracker; task board; pull/merge request; review checklist; code ownership; labels; milestones; release note
- 4
Build and release automation
- Build script; dependency cache; artifact; package registry; CI pipeline; test stage; security scan; deploy stage
8 more points
- Build script
- Dependency cache
- Artifact
- Package registry
- CI pipeline
- Test stage
- Security scan
- Deploy stage
- Reproducible builds; immutable artifact; version promotion; staging; canary; blue-green; rolling release; rollback
8 more points
- Reproducible builds
- Immutable artifact
- Version promotion
- Staging
- Canary
- Blue-green
- Rolling release
- Rollback
- Build script; dependency cache; artifact; package registry; CI pipeline; test stage; security scan; deploy stage
- 5
Infrastructure as code
- Declarative vs imperative config; infrastructure provisioning; configuration management; secrets; state file; drift
6 more points
- Declarative vs imperative config
- Infrastructure provisioning
- Configuration management
- Secrets
- State file
- Drift
- Containers; container images; registries; orchestration; Kubernetes concepts; service discovery; ingress; autoscaling
8 more points
- Containers
- Container images
- Registries
- Orchestration
- Kubernetes concepts
- Service discovery
- Ingress
- Autoscaling
- Declarative vs imperative config; infrastructure provisioning; configuration management; secrets; state file; drift
- 6
Delivery and operating models
- DevOps; DevSecOps; GitOps; platform engineering; developer experience; paved roads; self- service platform
7 more points
- DevOps
- DevSecOps
- GitOps
- Platform engineering
- Developer experience
- Paved roads
- Self- service platform
- SRE; service-level indicator/objective/agreement; error budget; toil; incident command; postmortem without blame
6 more points
- SRE
- Service-level indicator/objective/agreement
- Error budget
- Toil
- Incident command
- Postmortem without blame
- DevOps; DevSecOps; GitOps; platform engineering; developer experience; paved roads; self- service platform
- 7
Observability and operations
- Logs; metrics; traces; events; dashboards; alerting; correlation IDs; distributed tracing; telemetry sampling
9 more points
- Logs
- Metrics
- Traces
- Events
- Dashboards
- Alerting
- Correlation IDs
- Distributed tracing
- Telemetry sampling
- Availability; latency; saturation; throughput; capacity planning; performance regression; on- call rotation
7 more points
- Availability
- Latency
- Saturation
- Throughput
- Capacity planning
- Performance regression
- On- call rotation
- Logs; metrics; traces; events; dashboards; alerting; correlation IDs; distributed tracing; telemetry sampling
- 8
Incident and resilience management
- Detection; triage; severity; escalation; mitigation; communication; recovery; root-cause analysis; action tracking
9 more points
- Detection
- Triage
- Severity
- Escalation
- Mitigation
- Communication
- Recovery
- Root-cause analysis
- Action tracking
- Backups; restore tests; failover; disaster recovery; business continuity; chaos testing; resilience game days
7 more points
- Backups
- Restore tests
- Failover
- Disaster recovery
- Business continuity
- Chaos testing
- Resilience game days
- Detection; triage; severity; escalation; mitigation; communication; recovery; root-cause analysis; action tracking
- 9
Software supply-chain security
- SBOM; provenance; signed builds; dependency pinning; secret scanning; artifact attestations; trusted builders
7 more points
- SBOM
- Provenance
- Signed builds
- Dependency pinning
- Secret scanning
- Artifact attestations
- Trusted builders
- SLSA concepts; build isolation; dependency confusion; typosquatting; compromised maintainer; patch response
6 more points
- SLSA concepts
- Build isolation
- Dependency confusion
- Typosquatting
- Compromised maintainer
- Patch response
- SBOM; provenance; signed builds; dependency pinning; secret scanning; artifact attestations; trusted builders
- 10
FinOps and sustainability
- Cost allocation; unit economics; capacity rightsizing; autoscaling; idle resource detection; budget alerts
6 more points
- Cost allocation
- Unit economics
- Capacity rightsizing
- Autoscaling
- Idle resource detection
- Budget alerts
- Energy use; carbon-aware workloads; regional constraints; service lifecycle and decommissioning
4 more points
- Energy use
- Carbon-aware workloads
- Regional constraints
- Service lifecycle and decommissioning
- Cost allocation; unit economics; capacity rightsizing; autoscaling; idle resource detection; budget alerts
