Buzzword Bingo!
1. Continuous Integration (CI)
The practice of frequently integrating code changes into a shared repository, where automated builds and tests are run to detect issues early in the development cycle.
2. Continuous Delivery (CD)
An extension of CI, where code changes are automatically prepared for release into production. Every stage is automated, ensuring that code can be safely deployed at any time.
3. Infrastructure as Code (IaC)
The management of infrastructure (networks, servers, etc.) using machine-readable configuration files, rather than through physical hardware configuration or interactive configuration tools.
4. Containers
A lightweight, portable, and self-sufficient software package that includes everything needed to run an application, isolating it from other software on the system.
5. Kubernetes
An open-source container orchestration platform for automating deployment, scaling, and managing containerized applications.
6. Microservices
A design architecture where a system is divided into small, self-contained services that can be developed, deployed, and scaled independently.
7. DevSecOps
An evolution of DevOps that integrates security practices into every stage of the development lifecycle, ensuring that security is a shared responsibility.
8. Service Mesh
A dedicated infrastructure layer that manages service-to-service communication within a microservices architecture, providing observability, security, and traffic management.
9. GitOps
A practice of using Git as the single source of truth for managing infrastructure and application deployment. Changes to the infrastructure are made via pull requests, which are automatically applied by deployment pipelines.
10. Observability
The ability to measure the internal states of a system based on the external outputs, including metrics, logs, and traces, to monitor system performance and diagnose issues.
11. Blue-Green Deployment
A release management strategy that involves running two production environments—one “blue” (current version) and one “green” (new version)—and switching traffic from blue to green once the new version is verified.
12. Canary Release
A deployment strategy where a new software version is released to a small subset of users first, allowing it to be tested in production without exposing the entire user base to potential risks.
13. Serverless Computing
A cloud-computing model where developers write code without worrying about the underlying infrastructure. The cloud provider manages server provisioning and scaling automatically.
14. Artifact
Any by-product created during the software development process, such as binaries, container images, or compiled packages, that can be reused or deployed.
15. Load Balancer
A device or software application that distributes network or application traffic across multiple servers to ensure reliability and scalability.
16. Pipeline
A series of automated steps that take code from version control, through testing, and finally into production, ensuring that each change is safely integrated and delivered.
17. SRE (Site Reliability Engineering)
A discipline that applies software engineering practices to operations to ensure system reliability, performance, and scalability through automation and proactive management.
18. Rolling Deployment
A deployment strategy where a new version of the application is gradually rolled out by replacing instances of the older version, ensuring continuous availability.
19. Cluster
A group of interconnected servers that work together as a single unit to run applications, manage workloads, and provide high availability.
20. Prometheus
An open-source monitoring and alerting toolkit designed specifically for reliability and scalability, commonly used in cloud-native environments for gathering metrics and providing time-series data.
Glossary
Search
Latest Posts
Latest Comments
No comments to show.