Programmer's terminology
Over the years of development and programming, many terms have appeared in the world of programmers, and I will write many parts to try to explain all types of terms, so let’s begin:
# | Terminology | Description |
|---|---|---|
1 | Deployment | The process of releasing software changes into a production environment. |
2 | Blue-Green Deployment | A deployment strategy where two identical production environments, blue and green, are maintained. One environment is active while the other is idle. |
3 | Canary Deployment | A deployment strategy that releases a new version of the software to a small subset of users before rolling it out to the entire infrastructure. |
4 | Continuous Integration (CI) | A development practice where developers integrate code changes into a shared repository frequently, usually multiple times daily. |
5 | Continuous Deployment (CD) | A strategy to automatically release software changes into the production environment after passing automated tests. |
6 | Rollback | The process of reverting a system or software to a previous state or version. |
7 | Roll forward | Process of applying incremental updates or changes to move a system or software to a more current state. |
8 | Hotfix | An update to address a critical bug or security vulnerability in a software system is usually applied urgently. |
9 | Release | A version of a software product that is made available to customers for use. |
10 | Version Control | The management of changes to documents, computer programs, large websites, and other collections of information. |
11 | Artifact | A deployable component of a software application, such as a compiled binary or a packaged file. |
12 | Scalability | The capability of a system, network, or process to handle a growing amount of work or its potential to be enlarged to accommodate that growth. |
13 | DevOps | A set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle. |
14 | Containerization | A technology that encapsulates an application with its dependencies and runtime environment, allowing it to be run consistently across various computing environments. |
15 | Microservices | A software development technique where an application is composed of small, independent services that communicate over well-defined APIs. |
16 | Infrastructure as Code (IaC) | Managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. |
17 | Automation | The use of technology to perform tasks with minimal human intervention. |
18 | Load Balancing | Distributing incoming network traffic across multiple servers to ensure no single server is overwhelmed, improving reliability and redundancy. |
19 | High Availability | A system or component that is continuously operational for a desirably long length of time. |
20 | Redundancy | A set of changes to a computer program or its supporting data designed to update, fix, or improve it. |
21 | Incident Management | The process of identifying, analyzing, and resolving incidents to prevent future recurrences. |
22 | Disaster Recovery | The process of regaining access to the data, hardware, and software necessary to resume critical business operations after a natural or human-induced disaster. |
23 | Monitoring | The process of observing and checking the status of a system, network, or application to ensure smooth operation and detect issues. |
24 | Alerting | Notifying appropriate individuals or systems about events that require attention or action. |
25 | Scalability | The capability of a system, network, or process to handle a growing amount of work or its potential to be enlarged to accommodate that growth. |
26 | Serverless Computing | A cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. |
27 | Elasticity | The ability of a system to automatically provision and release resources to match the current workload demands. |
28 | Server Farm | A group of networked servers used for remote processing or data storage. |
29 | Virtualization | The creation of a virtual (rather than actual) version of something, such as an operating system, server, storage device, or network resources. |
30 | Patch | A set of changes to a computer program or its supporting data designed to update, fix, or improve it. |
