diff --git a/content/en/_TEMPLATE.md b/content/en/_TEMPLATE.md index 334627ffde..1a6b8f05ae 100644 --- a/content/en/_TEMPLATE.md +++ b/content/en/_TEMPLATE.md @@ -4,8 +4,6 @@ status: Feedback Appreciated category: concept --- -## What it is - Quick summary of the concept and what it is. ## Problem it addresses diff --git a/content/en/agile-software-development.md b/content/en/agile-software-development.md index a13512ed03..bea3f19dfa 100644 --- a/content/en/agile-software-development.md +++ b/content/en/agile-software-development.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "", ""] --- -## What it is - A set of practices that emphasize iterative development cycles and self-organizing teams. In contrast to waterfall-like projects where value is generated only at the very end of a project, agile software development focuses on a continuous, incremental delivery of value and diff --git a/content/en/api-gateway.md b/content/en/api-gateway.md index c9dde663da..5ee58d8842 100644 --- a/content/en/api-gateway.md +++ b/content/en/api-gateway.md @@ -5,8 +5,6 @@ category: technology tags: ["networking", "", ""] --- -## What it is - An [API](/application-programming-interface/) gateway is a tool that aggregates unique application APIs, making them all available in one place. It allows organizations to move key functions, diff --git a/content/en/application-programming-interface.md b/content/en/application-programming-interface.md index 379792008b..ccb2c70396 100644 --- a/content/en/application-programming-interface.md +++ b/content/en/application-programming-interface.md @@ -5,8 +5,6 @@ category: technology tags: ["architecture", "fundamental", ""] --- -## What it is - An API is a way for computer programs to interact with each other. Just as humans interact with a website via a web page, an API allows computer programs to interact with each other. Unlike human interactions, APIs have limitations on what can and cannot be asked of them. diff --git a/content/en/bare-metal-machine.md b/content/en/bare-metal-machine.md index 92dbc27103..6369abe235 100644 --- a/content/en/bare-metal-machine.md +++ b/content/en/bare-metal-machine.md @@ -5,8 +5,6 @@ category: technology tags: ["infrastructure", "", ""] --- -## What it is - Bare metal refers to a physical computer, more specifically a server, that has one, and only one, operating system. The distinction is important in modern computing because many, if not most, servers are [virtual machines](/virtual-machine/). A physical server is typically a fairly large computer with powerful hardware built-in. diff --git a/content/en/blue-green-deployment.md b/content/en/blue-green-deployment.md index 24274bf89f..f0fc7f4b7c 100644 --- a/content/en/blue-green-deployment.md +++ b/content/en/blue-green-deployment.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "application", ""] --- -## What it is - Blue-green deployment is a strategy for updating running computer systems with minimal downtime. The operator maintains two environments, dubbed “blue” and “green”. One serves production traffic (the version all users are currently using), whilst the other is updated. diff --git a/content/en/canary-deployment.md b/content/en/canary-deployment.md index 6006eb16d9..dfb9da5599 100644 --- a/content/en/canary-deployment.md +++ b/content/en/canary-deployment.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "application", ""] --- -## What it is - Canary deployments is a deployment strategy that starts with two environments: one with live traffic and the other containing the updated code without live traffic. The traffic is gradually moved from the original version of the application to the updated version. diff --git a/content/en/chaos-engineering.md b/content/en/chaos-engineering.md index e01cf06d42..99bc528637 100644 --- a/content/en/chaos-engineering.md +++ b/content/en/chaos-engineering.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "", ""] --- -## What it is - Chaos Engineering or CE is the discipline of experimenting on a [distributed system](/distributed-systems/) in production to build confidence in the system's capability to withstand turbulent and unexpected conditions. diff --git a/content/en/client-server-architecture.md b/content/en/client-server-architecture.md index 0a7bbfa1fb..84e4aef028 100644 --- a/content/en/client-server-architecture.md +++ b/content/en/client-server-architecture.md @@ -5,8 +5,6 @@ category: concept tags: ["architecture", "fundamental", ""] --- -## What it is - In a client-server architecture, the logic (or code) that makes up an application is split between two or more components: a client that asks for work to be done (e.g. the Gmail web application running in your web browser), diff --git a/content/en/cloud-computing.md b/content/en/cloud-computing.md index 708c9b6be5..e8152f93fd 100644 --- a/content/en/cloud-computing.md +++ b/content/en/cloud-computing.md @@ -5,8 +5,6 @@ category: concept tags: ["infrastructure", "fundamental", ""] --- -## What it is - Cloud computing offers compute resources like CPU, network, and disk capabilities on-demand over the internet, allowing users to access and use computing power in a remote physical location. We generally differentiate between private and public cloud, depending on whether the cloud infrastructure is exclusively dedicated to an organization or shared for open public services. diff --git a/content/en/cloud-native-apps.md b/content/en/cloud-native-apps.md index 0c5a8c7777..513bb17102 100644 --- a/content/en/cloud-native-apps.md +++ b/content/en/cloud-native-apps.md @@ -5,8 +5,6 @@ category: concept tags: ["application", "fundamental", ""] --- -## What it is - Cloud native applications are specifically designed to take advantage of innovations in [cloud computing](/cloud-computing/). These applications integrate easily with their respective cloud architectures, taking advantage of the cloud’s resources and [scaling](/scalability/) capabilities. diff --git a/content/en/cloud-native-security.md b/content/en/cloud-native-security.md index e3cc8eb775..a79ccb1b21 100644 --- a/content/en/cloud-native-security.md +++ b/content/en/cloud-native-security.md @@ -5,8 +5,6 @@ category: concept tags: ["security", "", ""] --- -## What it is - Cloud native security is an approach that builds security into [cloud native applications](/cloud-native-apps/). It ensures that security is part of the entire application lifecycle from development to production. Cloud native security seeks to ensure the same standards as traditional security models diff --git a/content/en/cloud-native-tech.md b/content/en/cloud-native-tech.md index 65aa54cfdb..19d63771f0 100644 --- a/content/en/cloud-native-tech.md +++ b/content/en/cloud-native-tech.md @@ -5,8 +5,6 @@ category: Concept tags: ["fundamental", "", ""] --- -## What it is - Cloud native technologies, also referred to as the cloud native stack, are the technologies used to build [cloud native applications](/cloud-native-apps/). These technologies enable organizations to build and run scalable applications in modern and dynamic environments diff --git a/content/en/cluster.md b/content/en/cluster.md index 055260586b..d4eec0a041 100644 --- a/content/en/cluster.md +++ b/content/en/cluster.md @@ -5,8 +5,6 @@ category: Concept tags: ["infrastructure", "fundamental", ""] --- -## What it is - A cluster is a group of computers or applications that work together towards a common goal. In the context of cloud native computing, the term is most often applied to [Kubernetes](/kubernetes/). A Kubernetes cluster is a set of services (or workloads) that run in their own containers, usually on different machines. diff --git a/content/en/container-image.md b/content/en/container-image.md index 5bcee26def..de43aec279 100644 --- a/content/en/container-image.md +++ b/content/en/container-image.md @@ -5,8 +5,6 @@ category: concept tags: ["", "", ""] --- -## What it is - A container image is an immutable, static file containing the dependencies for the creation of a [container](/container/). These dependencies may include a single executable binary file, system libraries, system tools, environment variables, and other required platform settings. diff --git a/content/en/container-orchestration.md b/content/en/container-orchestration.md index c0fe7989f9..504cdec363 100644 --- a/content/en/container-orchestration.md +++ b/content/en/container-orchestration.md @@ -4,8 +4,6 @@ status: Completed category: Concept --- -## What it is - [Container](/container/) orchestration refers to managing and automating the lifecycle of containerized applications in dynamic environments. It's executed through a container orchestrator (in most cases, [Kubernetes](/kubernetes)), which enables deployments, (auto)scaling, auto-healing, and monitoring. Orchestration is a metaphor: diff --git a/content/en/container.md b/content/en/container.md index 29ec749c52..6cb69fe323 100644 --- a/content/en/container.md +++ b/content/en/container.md @@ -5,8 +5,6 @@ category: technology tags: ["application", "fundamental", ""] --- -## What it is - A container is a running process with resource and capability constraints managed by a computer’s operating system. The files available to the container process are packaged as a container image. Containers run adjacent to each other on the same machine, diff --git a/content/en/containerization.md b/content/en/containerization.md index 92d2e4b4fb..60b01eefe3 100644 --- a/content/en/containerization.md +++ b/content/en/containerization.md @@ -5,8 +5,6 @@ category: Technology tags: ["application", "", ""] --- -## What it is - Containerization is the process of bundling an application and its dependencies into a container image. The container build process requires adherence to the [Open Container Initiative](https://opencontainers.org) (OCI) standard. As long as the output is a container image that adheres to this standard, which containerization tool is used doesn't matter. diff --git a/content/en/containers-as-a-service.md b/content/en/containers-as-a-service.md index 91f0db0167..0ecfcd64fe 100644 --- a/content/en/containers-as-a-service.md +++ b/content/en/containers-as-a-service.md @@ -6,8 +6,6 @@ draft: true tags: ["platform", "", ""] --- -## What it is - Containers-as-a-Service (CaaS) is a cloud service that helps manage and deploy apps using [container](/container/)-based [abstraction](/abstraction/). This service can be deployed on-premises or in the cloud. diff --git a/content/en/continuous-delivery.md b/content/en/continuous-delivery.md index 67bf91e798..6445620523 100644 --- a/content/en/continuous-delivery.md +++ b/content/en/continuous-delivery.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "application", ""] --- -## What it is - Continuous delivery, often abbreviated as CD, is a set of practices in which code changes are automatically deployed into an acceptance environment (or, in the case of continuous deployment, into production). diff --git a/content/en/continuous-deployment.md b/content/en/continuous-deployment.md index 5edd1f1516..f6a91f0a3e 100644 --- a/content/en/continuous-deployment.md +++ b/content/en/continuous-deployment.md @@ -5,8 +5,6 @@ category: concept tags: ["application", "methodology", ""] --- -## What it is - Continuous deployment, often abbreviated as CD, goes a step further than [continuous delivery](/continuous-delivery/) by deploying finished software directly to production. Continuous deployment (CD) goes hand in hand with [continuous integration](/continuous-integration/) (CI), diff --git a/content/en/continuous-integration.md b/content/en/continuous-integration.md index f4035f5c5f..b868c12e01 100644 --- a/content/en/continuous-integration.md +++ b/content/en/continuous-integration.md @@ -5,8 +5,6 @@ category: concept tags: ["application", "methodology", ""] --- -## What it is - Continuous integration, often abbreviated as CI, is the practice of integrating code changes as regularly as possible. CI is a prerequisite for [continuous delivery](/continuous-delivery/) (CD). Traditionally, the CI process begins when code changes are committed to a source control system (Git, Mercurial, or Subversion) diff --git a/content/en/data-center.md b/content/en/data-center.md index 59a0cbaa78..096b070051 100644 --- a/content/en/data-center.md +++ b/content/en/data-center.md @@ -5,8 +5,6 @@ category: Technology tags: ["infrastructure", "fundamental", ""] --- -## What it is - A datacenter is a specialized building or facility designed to house computers, most often servers. These datacenters tend to be connected to high-speed internet lines, especially when focused on [cloud computing](/cloud-computing/). The buildings housing datacenters are equipped to maintain service even during adverse events, including generators that provide power during outages and powerful air conditioning that keep the heat-producing computers cool. diff --git a/content/en/database-as-a-service.md b/content/en/database-as-a-service.md index 58f298ab68..e8fc195bd0 100644 --- a/content/en/database-as-a-service.md +++ b/content/en/database-as-a-service.md @@ -6,8 +6,6 @@ draft: true tags: ["", "", ""] --- -## What it is - Database-as-a-Service (DBaaS) is a service managed by a [cloud](/cloud-computing/) operator (public or private) that supports applications without requiring the application team to perform traditional database administration functions. diff --git a/content/en/debugging.md b/content/en/debugging.md index 4545902109..59e3b931ae 100644 --- a/content/en/debugging.md +++ b/content/en/debugging.md @@ -6,8 +6,6 @@ draft: true tags: ["application", "methodology", ""] --- -## What it is - Debugging is the process or activity of finding and resolving bugs (or errors) from computer programs, software, or systems to get the desired result. A bug is a defect or a problem leading to incorrect or unexpected results. diff --git a/content/en/devops.md b/content/en/devops.md index 6dc170f1a9..271e0147fb 100644 --- a/content/en/devops.md +++ b/content/en/devops.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "", ""] --- -## What it is - DevOps is a methodology in which teams own the entire process from application development to production operations, hence DevOps. It goes beyond implementing a set of technologies and requires a complete shift in culture and processes. DevOps calls for groups of engineers that work on small components (versus an entire feature), decreasing handoffs – a common source of errors. diff --git a/content/en/devsecops.md b/content/en/devsecops.md index 9a5fb969a9..0185989d88 100644 --- a/content/en/devsecops.md +++ b/content/en/devsecops.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "security", ""] --- -## What it is - The term DevSecOps refers to a cultural merger of the development, operational, and security responsibilities. It extends the [DevOps](/devops/) approach to include security priorities with minimal to no disruption in the developer and operational workflow. diff --git a/content/en/digital-certificate.md b/content/en/digital-certificate.md index 3b58b9905d..10627da3ec 100644 --- a/content/en/digital-certificate.md +++ b/content/en/digital-certificate.md @@ -5,8 +5,6 @@ category: technology tags: ["security", "", ""] --- -## What it is - A (digital) certificate — also often referred to as a public key certificate, or SSL certificate — is a digital document used to help secure communications over the network. Certificates allow us to know that the particular entity we're communicating with is who they say they are. They also allow us to ensure that our communications are private by encrypting the data we send and receive. diff --git a/content/en/distributed-apps.md b/content/en/distributed-apps.md index ac57c62d43..ccf00e69bf 100644 --- a/content/en/distributed-apps.md +++ b/content/en/distributed-apps.md @@ -5,8 +5,6 @@ category: concept tags: ["architecture", "", ""] --- -## What it is - A distributed application is an application where the functionality is broken down into multiple smaller independent parts. Distributed applications are usually composed of individual [microservices](/microservices/) that handle different concerns within the broader application. diff --git a/content/en/distributed-systems.md b/content/en/distributed-systems.md index 358b03b11c..474dbb9528 100644 --- a/content/en/distributed-systems.md +++ b/content/en/distributed-systems.md @@ -5,8 +5,6 @@ category: concept tags: ["architecture", "", ""] --- -## What it is - A distributed system is a collection of autonomous computing elements connected over a network that appears to users as a single coherent system. Generally referred to as [nodes](/nodes/), these components can be hardware devices (e.g. computers, mobile phones) or software processes. diff --git a/content/en/ebpf.md b/content/en/ebpf.md index e46eaef503..a35f9be2f0 100644 --- a/content/en/ebpf.md +++ b/content/en/ebpf.md @@ -4,8 +4,6 @@ status: Completed category: architecture --- -## What it is - eBPF, or extended Berkeley Packet Filter, is a technology that allows small, sandboxed programs or scripts to run in the kernel space of a Linux system without having to change the kernel's source code or load Linux kernel modules. A Linux system has two spaces: the kernel and the user space. diff --git a/content/en/edge-computing.md b/content/en/edge-computing.md index 977a615242..a8c291df1e 100644 --- a/content/en/edge-computing.md +++ b/content/en/edge-computing.md @@ -4,8 +4,6 @@ status: Completed category: Technology --- -## What it is - Edge computing is a [distributed system](/distributed-systems/) approach that shifts some storage and computing capacity from the primary data center to the data source. The gathered data is computed locally (e.g., on a factory floor, in a store, or throughout a city) rather than sent to a centralized data center for processing and analysis. These local processing units or devices represent the system's edge, whereas the data center is its center. diff --git a/content/en/event-driven-architecture.md b/content/en/event-driven-architecture.md index 1b0b56fd6c..76f064b669 100644 --- a/content/en/event-driven-architecture.md +++ b/content/en/event-driven-architecture.md @@ -5,8 +5,6 @@ category: concept tags: ["architecture", "", ""] --- -## What it is - Event-driven architecture is a software architecture that promotes the creation, processing, and consumption of events. An event is any change to an application's state. For example, hailing a ride on a ride-sharing app represents an event. diff --git a/content/en/event-streaming.md b/content/en/event-streaming.md index 529920e64e..467d492dea 100644 --- a/content/en/event-streaming.md +++ b/content/en/event-streaming.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "networking", ""] --- -## What it is - Event streaming is an approach where software sends event data from one application to another to continuously communicate what they are doing. Picture a service broadcasting everything it does to all other services. Each activity taken by a service is referred to as an event, hence event streaming. diff --git a/content/en/firewall.md b/content/en/firewall.md index be1234bc73..1fb551763d 100644 --- a/content/en/firewall.md +++ b/content/en/firewall.md @@ -6,8 +6,6 @@ category: Technology tags: ["", "", ""] --- -## What it is - A firewall is a system that filters network traffic on the basis of specified rules. Firewalls can be hardware, software, or a combination of the two. diff --git a/content/en/function-as-a-service.md b/content/en/function-as-a-service.md index cffa8bfdbb..55cca7034a 100644 --- a/content/en/function-as-a-service.md +++ b/content/en/function-as-a-service.md @@ -5,8 +5,6 @@ category: Technology tags: ["infrastructure", "", ""] --- -## What it is - Function as a Service (FaaS) is a type of [serverless](/serverless/) [cloud computing](/cloud-computing/) [service](/service/) that allows executing code in response to events without maintaining the complex infrastructure diff --git a/content/en/gitops.md b/content/en/gitops.md index eed0abe284..251d4e5cf9 100644 --- a/content/en/gitops.md +++ b/content/en/gitops.md @@ -5,8 +5,6 @@ category: Concept tags: ["methodology", "", ""] --- -## What it is - GitOps is a set of best practices based on [shared principles](https://opengitops.dev/), applied to a workflow that depends on software agents that enable automation to reconcile a declared system state or configuration in a git repository. diff --git a/content/en/horizontal-scaling.md b/content/en/horizontal-scaling.md index e495a46a1e..99b1f71641 100644 --- a/content/en/horizontal-scaling.md +++ b/content/en/horizontal-scaling.md @@ -5,8 +5,6 @@ category: Concept tags: ["infrastructure", "", ""] --- -## What it is - Horizontal scaling is a technique where a system's capacity is increased by adding more [nodes](/nodes/) versus adding more compute resources to individual nodes (the latter being known as [vertical scaling](/vertical-scaling/)). Let's say, we have a system of 4GB RAM and want to increase its capacity to 16GB RAM, diff --git a/content/en/hypervisor.md b/content/en/hypervisor.md index cd16d6f70f..30ec7439f8 100644 --- a/content/en/hypervisor.md +++ b/content/en/hypervisor.md @@ -5,8 +5,6 @@ category: Technology tags: ["application", "", ""] --- -## What it is - A hypervisor enables [virtualization](/virtualization/) by taking the advantage of [bare metal machine](/bare-metal-machine/) resources (CPU, Memory, Network, and Storage), dividing them into sub-parts, diff --git a/content/en/infrastructure-as-a-service.md b/content/en/infrastructure-as-a-service.md index 7bf308bdb6..02ca02546b 100644 --- a/content/en/infrastructure-as-a-service.md +++ b/content/en/infrastructure-as-a-service.md @@ -5,8 +5,6 @@ category: Technology tags: ["infrastructure", "", ""] --- -## What it is - Infrastructure as a service, or IaaS, is a [cloud computing](/cloud-computing/) service model that offers [physical](/bare-metal-machine/) or [virtualized](/virtualization/) compute, storage, and network resources on-demand on a pay-as-you-go model. diff --git a/content/en/infrastructure-as-code.md b/content/en/infrastructure-as-code.md index a8c13bf8ab..bd63edade2 100644 --- a/content/en/infrastructure-as-code.md +++ b/content/en/infrastructure-as-code.md @@ -5,8 +5,6 @@ category: concept tags: ["infrastructure", "methodology", ""] --- -## What it is - Infrastructure as code is the practice of storing the definition of infrastructure as one or more files. This replaces the traditional model where infrastructure as a service is provisioned manually, usually through shell scripts or other configuration tools. diff --git a/content/en/kubernetes.md b/content/en/kubernetes.md index 0efca668b6..53c971bfc4 100644 --- a/content/en/kubernetes.md +++ b/content/en/kubernetes.md @@ -5,8 +5,6 @@ category: technology tags: ["infrastructure", "fundamental", ""] --- -## What it is - Kubernetes, often abbreviated as K8s, is an open source container orchestrator. It automates the lifecycle of containerized applications on modern infrastructures, functioning as a "datacenter operating system" that manages applications across a [distributed system](/distributed-systems/). diff --git a/content/en/load-balancer.md b/content/en/load-balancer.md index ba2f3a3924..861dd4033d 100644 --- a/content/en/load-balancer.md +++ b/content/en/load-balancer.md @@ -5,8 +5,6 @@ category: concept tags: ["infrastructure", "networking", ""] --- -## What it is - A load balancer is a tool that efficiently distributes incoming requests among multiple instances of an application. Take a [microservice](/microservices/) architecture for example, where each service can be [scaled horizontally](/horizontal-scaling/). A load balancer sits in front of a scaled microservice and ensures that no one instance gets the bulk of the requests. diff --git a/content/en/managed-services.md b/content/en/managed-services.md index 398a2f3597..8f541b9791 100644 --- a/content/en/managed-services.md +++ b/content/en/managed-services.md @@ -6,8 +6,6 @@ category: Technology tags: ["", "", ""] --- -## What it is - A managed service is a software offering where operations and management are taken care of by a third party. Examples include database as a service offerings like Amazon’s RDS or an external monitoring service like Datadog. diff --git a/content/en/microservices-architecture.md b/content/en/microservices-architecture.md index 804c623df3..9badc03ad0 100644 --- a/content/en/microservices-architecture.md +++ b/content/en/microservices-architecture.md @@ -4,8 +4,6 @@ status: Completed tags: ["architecture", "fundamental", ""] --- -## What it is - A microservices architecture is an architectural approach that breaks applications into individual independent (micro)[services](/service/), with each service focused on a specific functionality. These services work together closely, appearing to the end user as a single entity. Take Netflix as an example. diff --git a/content/en/monolithic-apps.md b/content/en/monolithic-apps.md index 42ebb8fbd4..c0bc6de7c7 100644 --- a/content/en/monolithic-apps.md +++ b/content/en/monolithic-apps.md @@ -5,8 +5,6 @@ category: concept tags: ["architecture", "fundamental", ""] --- -## What it is - A monolithic application contains all functionality in a single deployable program. This is often the simplest and easiest place to start when making an application. However, once the application grows in complexity, monoliths can become hard to maintain. diff --git a/content/en/multitenancy.md b/content/en/multitenancy.md index 21b38e94f4..de0773b66e 100644 --- a/content/en/multitenancy.md +++ b/content/en/multitenancy.md @@ -5,8 +5,6 @@ category: Property tags: ["architecture", "property", ""] --- -## What it is - Multitenancy (or multi-tenancy) refers to a single software installation that serves multiple tenants. A tenant is a user, application, or a group of users/applications that utilize the software to operate on their own data set. These tenants don't share data (unless explicitly instructed by the owner) and may not even be aware of one another. diff --git a/content/en/mutual-transport-layer-security.md b/content/en/mutual-transport-layer-security.md index de54fa9c82..9e50ae05bf 100644 --- a/content/en/mutual-transport-layer-security.md +++ b/content/en/mutual-transport-layer-security.md @@ -5,8 +5,6 @@ category: Concept tags: ["security", "networking", ""] --- -## What it is - Mutual TLS (mTLS) is a technique used to authenticate and encrypt messages sent between two [services](/service/). Mutual TLS is the standard [Transport Layer Security](/transport-layer-security/) (TLS) protocol but, instead of validating the identity of just one connection, both sides are validated. diff --git a/content/en/nodes.md b/content/en/nodes.md index 88a39b7c1a..434645ebf5 100644 --- a/content/en/nodes.md +++ b/content/en/nodes.md @@ -5,8 +5,6 @@ category: Concept tags: ["infrastructure", "fundamental", ""] --- -## What it is - A node is a computer that works in concert with other computers, or nodes, to accomplish a common task. Take your laptop, modem, and printer, for example. They are all connected over your wifi network communicating and collaborating, each representing one node. diff --git a/content/en/platform-as-a-service.md b/content/en/platform-as-a-service.md index 1734d310a1..47bbd94501 100644 --- a/content/en/platform-as-a-service.md +++ b/content/en/platform-as-a-service.md @@ -6,8 +6,6 @@ draft: true tags: ["fundamental", "platform", ""] --- -## What it is - A Platform as a Service, or PaaS, is an external platform for application development teams to deploy and run their apps. Heroku, Cloud Foundry, App Engine are examples of PaaS offerings. diff --git a/content/en/pod.md b/content/en/pod.md index 6bd9f4231d..307b2b0a8f 100644 --- a/content/en/pod.md +++ b/content/en/pod.md @@ -5,8 +5,6 @@ category: concept tags: ["infrastructure", "fundamental", ""] --- -## What it is - Within a [Kubernetes](/kubernetes/) environment, a pod acts as the most basic deployable unit. It represents an essential building block for deploying and managing containerized applications. Each pod contains a single application instance and can hold one or more [containers](/container/). diff --git a/content/en/policy-as-code.md b/content/en/policy-as-code.md index b2fa29d653..d542fcefc0 100644 --- a/content/en/policy-as-code.md +++ b/content/en/policy-as-code.md @@ -3,11 +3,8 @@ title: Policy as Code (PaC) status: Completed category: concept tags: ["methodology", "", ""] -draft: --- -## What it is - Policy as Code is the practice of storing the definition of policies as one or more files in machine-readable and processable form. This replaces the traditional model where policies are documented in human-readable form in separate documents. diff --git a/content/en/role-based-access-control.md b/content/en/role-based-access-control.md index 358c92eefa..c82e98e396 100644 --- a/content/en/role-based-access-control.md +++ b/content/en/role-based-access-control.md @@ -5,8 +5,6 @@ category: concept tags: ["security", "", ""] --- -## What it is - Role-based access control (RBAC) is a security method of managing user access to systems, networks, or resources based on their role within a team or a larger organization. RBAC empowers IT administrators to identify the necessary level of access for all users with a particular job function and assign those users a role with a predefined set of permissions. Organizations utilize RBAC to provide their employees with varying levels of access tailored to their roles and responsibilities. diff --git a/content/en/runtime.md b/content/en/runtime.md index 5ab304cad1..244af3c712 100644 --- a/content/en/runtime.md +++ b/content/en/runtime.md @@ -5,8 +5,6 @@ category: concept tags: ["application", "", ""] --- -## What it is - A runtime, in general, executes a piece of software. It is an [abstraction](/abstraction/) of the underlying operating system that translates the program's commands into respective actions for the operating system. diff --git a/content/en/security-chaos-engineering.md b/content/en/security-chaos-engineering.md index 646f57bce6..0affd08570 100644 --- a/content/en/security-chaos-engineering.md +++ b/content/en/security-chaos-engineering.md @@ -5,8 +5,6 @@ category: concept tags: ["security", "methodology", ""] --- -## What it is - Security Chaos Engineering or SCE is a discipline based on [Chaos Engineering](/chaos-engineering/). SCE performs proactive security experimentation on a distributed system to build confidence in the system's capability to withstand turbulent and malicious conditions. diff --git a/content/en/serverless.md b/content/en/serverless.md index 6ae8db19a1..c3fd0841db 100644 --- a/content/en/serverless.md +++ b/content/en/serverless.md @@ -5,8 +5,6 @@ Category: Technology tags: ["architecture", "", ""] --- -## What it is - Serverless is a cloud native development model that allows developers to build and run applications without having to manage servers. While servers do still exist within the serverless paradigm, they are [abstracted](/abstraction/) away from the application development process. diff --git a/content/en/service-discovery.md b/content/en/service-discovery.md index ecdfcbe79a..6a3cf46a09 100644 --- a/content/en/service-discovery.md +++ b/content/en/service-discovery.md @@ -5,8 +5,6 @@ category: concept tags: ["networking", "", ""] --- -## What it is - Service discovery is the process of finding individual instances that make up a service. A service discovery tool keeps track of the various nodes or endpoints that make up a service. diff --git a/content/en/service-mesh.md b/content/en/service-mesh.md index 46874021d1..31309f07ce 100644 --- a/content/en/service-mesh.md +++ b/content/en/service-mesh.md @@ -5,8 +5,6 @@ category: technology tags: ["networking", "", ""] --- -## What it is - In a [microservices](/microservices/) world, apps are broken down into multiple smaller [services](/service/) that communicate over a network. Just like your wifi network, computer networks are intrinsically unreliable, hackable, and often slow. Service meshes address this new set of challenges by managing traffic (i.e., communication) between services and diff --git a/content/en/service-proxy.md b/content/en/service-proxy.md index 9dabf5eb97..ed5ba6d9ed 100644 --- a/content/en/service-proxy.md +++ b/content/en/service-proxy.md @@ -5,8 +5,6 @@ category: technology tags: ["networking", "", ""] --- -## What it is - A service proxy intercepts traffic to or from a given [service](/service/), applies some logic to it, then forwards that traffic to another service. It essentially acts as a “go-between” that collects information about network traffic and/or applies rules to it. diff --git a/content/en/shift-left.md b/content/en/shift-left.md index 85ca1ceada..2f56f7919b 100644 --- a/content/en/shift-left.md +++ b/content/en/shift-left.md @@ -5,8 +5,6 @@ category: Concept tags: ["methodology", "", ""] --- -## What it is - Left in Shift Left refers to earlier stages in a software development lifecycle, thinking of the lifecycle as a line where stages are executed from left to right. Shift Left is the practice of implementing tests, security, or other development practices diff --git a/content/en/site-reliability-engineering.md b/content/en/site-reliability-engineering.md index 4385e28484..1753197f45 100644 --- a/content/en/site-reliability-engineering.md +++ b/content/en/site-reliability-engineering.md @@ -5,8 +5,6 @@ category: concept tags: ["methodology", "", ""] --- -## What it is - Site Reliability Engineering or SRE is a discipline that combines operations and software engineering. The latter is applied to infrastructure and operations problems, specifically. Meaning, instead of building product features, Site Reliability Engineers build systems to run applications. diff --git a/content/en/software-as-a-service.md b/content/en/software-as-a-service.md index 5258cdda48..2dbe79e80e 100644 --- a/content/en/software-as-a-service.md +++ b/content/en/software-as-a-service.md @@ -6,8 +6,6 @@ draft: true tags: ["fundamental", "platform", ""] --- -## What it is - Software as a service (SaaS) allows users to connect to and use cloud-based services over the Internet. Common examples are email, calendaring, and office tools (such as Gmail, Amazon Web Services, GitHub, Slack). SaaS provides complete software solutions on a pay-as-you-go basis. diff --git a/content/en/stateful-apps.md b/content/en/stateful-apps.md index 737a857c11..d4065b79c0 100644 --- a/content/en/stateful-apps.md +++ b/content/en/stateful-apps.md @@ -5,8 +5,6 @@ category: concept tags: ["fundamental", "application", ""] --- -## What it is - When we speak of stateful (and stateless) apps, state refers to any data the app needs to store to function as designed. Any kind of online shop that remembers your cart is a stateful app for example. diff --git a/content/en/stateless-apps.md b/content/en/stateless-apps.md index fe9fa3fb79..ea364457a2 100644 --- a/content/en/stateless-apps.md +++ b/content/en/stateless-apps.md @@ -5,8 +5,6 @@ category: technology tags: ["fundamental", "application", ""] --- -## What it is - A stateless application doesn’t save any client session (state) data on the server where the application lives. Each session is carried out as if it was the first time and responses are not dependent upon data from a previous session and provides functionality to use print services, CDN (Content Delivery Network) or the Web Servers diff --git a/content/en/style-guide/_index.md b/content/en/style-guide/_index.md index 554354395c..bab8303e7b 100644 --- a/content/en/style-guide/_index.md +++ b/content/en/style-guide/_index.md @@ -48,7 +48,6 @@ status: category: --- -## What it is A quick summary of the technology or concept. @@ -80,7 +79,7 @@ Valid values are: - Feedback Appreciated - Not Started -You can always open an issue against a completed definition. While a definition is in flux, its status will be changed to *Feedback Appreciated*. +You can always open an issue against a completed definition. While a definition is in flux, its status will be changed to *Feedback Appreciated*. Note that we should not localize the valid status values. ```md --- @@ -118,11 +117,11 @@ tags: ["tag 1", "tag 2", ""] ### Definition -#### Three subheadings +#### Two subheadings -The definitions for **technology** and **concept** categories contain three subheadings: +The definitions for **technology** and **concept** categories contain a quick summary and two subheadings: -- **What it is**: provide a short and clear overview of what we are talking about. +- (quick summary) provide a short and clear overview of what we are talking about. - **Problem it addresses**: focus on the problem, not the solution (that comes in the next section). Avoid mentioning the term that is defined. The problem focuses on *what* led us to need that thing. - **How it helps**: now, come back to the term. How does it address the problem described above? @@ -159,7 +158,7 @@ When appropriate, use **real-world examples** that help readers (especially non- When used in your definition, always **link to existing glossary terms** (only the first mention should be hyperlinked). -**Example**: look at the “What it is” section of the [service mesh definition](/service-mesh/). +**Example**: look at the summary section of the [service mesh definition](/service-mesh/). It links back to the definitions of microservices, service, reliability, and observability. Additionally, it uses a real-world example comparing network challenges in a microservices environment (something non-technical people can't relate to) to wifi problems (something anyone using a laptop can understand). diff --git a/content/en/transport-layer-security.md b/content/en/transport-layer-security.md index 2fd122fa62..e12a6d370e 100644 --- a/content/en/transport-layer-security.md +++ b/content/en/transport-layer-security.md @@ -5,8 +5,6 @@ category: Concept tags: ["security", "networking", ""] --- -## What it is - Transport Layer Security (TLS) is a protocol designed to provide increased security to communication over a network. It ensures the secure delivery of data sent over the Internet, avoiding possible monitoring and/or alteration of the data. diff --git a/content/en/version-control.md b/content/en/version-control.md index b236985263..977e514c2b 100644 --- a/content/en/version-control.md +++ b/content/en/version-control.md @@ -6,8 +6,6 @@ draft: true tags: ["methodology", "", ""] --- -## What it is - Source control (or version control) is the practice of tracking and managing changes to a document. It is a system that records changes to a file or set of files over time so that you can recall specific versions later. diff --git a/content/en/vertical-scaling.md b/content/en/vertical-scaling.md index 573fd34864..31d071eb5a 100644 --- a/content/en/vertical-scaling.md +++ b/content/en/vertical-scaling.md @@ -5,8 +5,6 @@ category: Concept tags: ["infrastructure", "", ""] --- -## What it is - Vertical scaling, also known as "scaling up and down", is a technique where a system's capacity is increased by adding CPU and memory to individual [nodes](/nodes/) as the workload increases. Let's say, you have a computer of 4GB RAM and want to increase its capacity to 16GB RAM, diff --git a/content/en/virtual-machine.md b/content/en/virtual-machine.md index 0c03841df5..1f27483723 100644 --- a/content/en/virtual-machine.md +++ b/content/en/virtual-machine.md @@ -5,8 +5,6 @@ category: Technology tags: ["fundamental", "infrastructure", ""] --- -## What it is - A virtual machine (VM) is a computer and its operating system that is not bound to a particular piece of hardware. VMs rely on [virtualization](/virtualization/) to carve a single physical computer into multiple virtual computers. diff --git a/content/en/virtualization.md b/content/en/virtualization.md index 8a3c694d55..708b5b1a31 100644 --- a/content/en/virtualization.md +++ b/content/en/virtualization.md @@ -5,8 +5,6 @@ category: technology tags: ["fundamental", "infrastructure", "methodology"] --- -## What it is - Virtualization, in the context of cloud native computing, refers to the process of taking a physical computer, sometimes called a server, and allowing it to run multiple isolated operating systems. diff --git a/content/en/zero-trust-architecture.md b/content/en/zero-trust-architecture.md index 3d6d606fae..b00cbf489d 100644 --- a/content/en/zero-trust-architecture.md +++ b/content/en/zero-trust-architecture.md @@ -5,8 +5,6 @@ category: Concept tags: ["security", "", ""] --- -## What it is - Zero trust architecture prescribes to an approach to the design and implementation of IT systems where trust is completely removed. The core principle being "never trust, always verify", devices or systems themselves,