Principles, concepts and practices
Here’s the text from your image:
Downtime → a period during which a system, website, or service is not operational. Used to plan maintenance, upgrades, migrations.
Toil → refers to repetitive manual and unproductive work that doesn’t add value to organization.
Latency → the time it takes for a packet of data (to travel) from source to destination.
Outage → a period when a service/system is unavailable due to an unplanned incident, e.g., HW issue, HW failure, SW bug.
Bottleneck → a point of blockage in a system that slows down the overall process, limits throughput and efficiency.
Lag → delays both initiation and execution.
Overhead → the extra time, memory, bandwidth, or other resources required by a system to perform its tasks which does not contribute to main function of tasks.
Do you want me to also rewrite these in a cleaner, professional glossary format?
Here’s the text from your image:
Redundancy → the inclusion of extra components to increase reliability and provide backup in case of failure. Example: K8S HAA
Throttling → intentionally slowing down processes or requests to avoid overloading systems.
Spike → a sudden increase in workload or demand on a system.
Backlog → unfulfilled tasks that have not been completed.
Capacity Planning → a process of determining production capacity needed by an organization to meet changing demands for its products.
Concurrency → the ability of a system to handle multiple tasks or operations simultaneously.
Failover → the automatic switching to a standby system upon the failure of the primary active system.
Here’s the text from your image:
MTBF → Mean Time Between Failure (average time).
MTTR → Mean (average) time to repair/recover — the average time to repair a failed system.
Scalability → the capability of a system to handle growing amounts of work or load.
Throughput → the amount of data processed by a system in a given period.
Load balancing → the process of distributing workload across multiple resources to optimize performance & prevent overload.
Bug → error/flaw/fault in software that produces an unexpected result.
Resilience → the ability of a system to recover function from failure and continue to operate.
Fail-safe → redundant systems/failure mechanisms to have.
Agile → a methodology for software development — their emphasis/focus on iterative development, collaboration.
Scrum → an Agile framework for managing work involving iterative progress through regular, time-boxed sprints.
Here’s the text from your image:
KPI (Key Performance Indicator)
Microservices → an architectural style that structures an application as a collection of loosely coupled, independently deployable services.
Virtualization → a technique of splitting a physical hardware resource, such as memory, CPU, disk, into multiple virtual machines (VMs) to utilize resources efficiently.
Consolidation → combining workloads to better utilize resources.
Hypervisor (software) → enables virtualization.
Cloud →
Capex (Capital Expenditure): upfront cost (equipment/hardware).
Opex (Operational Expenditure): ongoing cost (management/human).
GitOps = Is a practice where Git is considered as the single source of truth for infra/app delivery.
Multi-tenant SaaS:
A single instance of the application serves multiple customers (tenants).
Do you want me to now merge all four images into one clean, professional glossary document?
Last updated