chore: remove duplicated lines

Signed-off-by: Seokho Son <shsongist@gmail.com>
kaitoii11 · Nov 30, 2023 · e57ed31 · e57ed31
1 parent 2337701
commit e57ed31
Show file tree

Hide file tree

Showing 71 changed files with 5 additions and 76 deletions.
diff --git a/content/en/_TEMPLATE.md b/content/en/_TEMPLATE.md
@@ -4,8 +4,7 @@ status: Feedback Appreciated
 category: concept
 ---
 
-
-Quick summary of the concept.
+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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: technology
 tags: ["networking", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: technology
 tags: ["architecture", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: technology
 tags: ["infrastructure", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "application", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "application", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["architecture", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["infrastructure", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["application", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["security", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["fundamental", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["infrastructure", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["", "", ""]
 ---
 
-
 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
@@ -4,7 +4,6 @@ status: Completed
 category: Concept
 ---
 
-
 [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
@@ -5,7 +5,6 @@ category: technology
 tags: ["application", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Technology
 tags: ["application", "", ""]
 ---
 
-
 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
@@ -6,7 +6,6 @@ draft: true
 tags: ["platform", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "application", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["application", "methodology", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["application", "methodology", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Technology
 tags: ["infrastructure", "fundamental", ""]
 ---
 
-
 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
@@ -6,7 +6,6 @@ draft: true
 tags: ["", "", ""]
 ---
 
-
 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
@@ -6,7 +6,6 @@ draft: true
 tags: ["application", "methodology", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "security", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: technology
 tags: ["security", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["architecture", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["architecture", "", ""]
 ---
 
-
 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
@@ -4,7 +4,6 @@ status: Completed
 category: architecture
 ---
 
-
 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
@@ -4,7 +4,6 @@ status: Completed
 category: Technology
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["architecture", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["methodology", "networking", ""]
 ---
 
-
 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
@@ -6,7 +6,6 @@ category: Technology
 tags: ["", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Technology
 tags: ["infrastructure", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["methodology", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["infrastructure", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Technology
 tags: ["application", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Technology
 tags: ["infrastructure", "", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["infrastructure", "methodology", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: technology
 tags: ["infrastructure", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["infrastructure", "networking", ""]
 ---
 
-
 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
@@ -6,7 +6,6 @@ category: Technology
 tags: ["", "", ""]
 ---
 
-
 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
@@ -4,7 +4,6 @@ status: Completed
 tags: ["architecture", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: concept
 tags: ["architecture", "fundamental", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Property
 tags: ["architecture", "property", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["security", "networking", ""]
 ---
 
-
 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
@@ -5,7 +5,6 @@ category: Concept
 tags: ["infrastructure", "fundamental", ""]
 ---
 
-
 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.
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,7 +5,6 @@ category: concept @@
     tags: ["methodology", "", ""]
     ---
     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.
@@ Expand Down @@