[ja] Merge main into dev-ja to sync-up

.gitignore

@@ -4,6 +4,7 @@ resources/
 node_modules/
 .hugo_build.lock
 .DS_Store
+pagefind
 
 # Local Netlify folder
 .netlify

Makefile

@@ -0,0 +1,28 @@
+serve:
+	hugo server \
+		--disableFastRender \
+		--buildDrafts \
+		--buildFuture \
+		--ignoreCache
+		--printI18nWarnings \
+		--printMemoryUsage \
+		--printPathWarnings \
+		--printUnusedTemplates \
+		--templateMetrics \
+		--templateMetricsHints \
+		--gc
+
+production-build:
+	git submodule update --init --recursive
+	hugo \
+		--minify
+	npx -y pagefind --site public
+
+preview-build:
+	git submodule update --init --recursive
+	hugo \
+		--baseURL $(DEPLOY_PRIME_URL) \
+		--buildDrafts \
+		--buildFuture \
+		--minify
+	npx -y pagefind --site public

README.md

@@ -50,6 +50,6 @@ git submodule update --init --recursive
 npm install
 ```
 
-You can then run the site using `npm run serve` (select "[Hugo]").
+You can then run the site using `npm run serve` (select "[Hugo]"). To have the site run locally with a functioning local search, run `npm run serve:with-pagefind`.
 
 [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?repo=cncf/glossary)

assets/js/search.js

@@ -0,0 +1,43 @@
+/*
+Copyright 2018 Google LLC
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+*/
+
+(function($) {
+
+    'use strict';
+
+    var Search = {
+        init: function() {
+            $(document).ready(function() {
+               $(document).on('keypress', '.td-search-input', function(e) {
+                    if (e.keyCode !== 13) {
+                        return
+                    }
+
+                    var query = $(this).val();
+                    var searchPage = $(this).data('search-page') + "?q=" + query;
+                    document.location = searchPage;
+
+                    return false;
+                });
+
+            });
+        },
+    };
+
+    Search.init();
+
+
+}(jQuery));

assets/scss/_search.scss

@@ -100,3 +100,14 @@
 	}
 
 }
+
+.pagefind-ui__result-link {
+	color: $link-color !important;
+}
+.pagefind-ui__search-clear {
+	padding-left: 20px !important;
+	padding-right: 20px !important;
+}
+#search {
+	margin-top: 40px;
+}

config.toml

@@ -132,43 +132,51 @@ weight = 9
 [languages.pt-br.params]
 description = "O Projeto CNCF Glossário Cloud Native se destina a ser usado como uma referência para termos comuns usados ao falar sobre aplicações nativas de nuvem."
 
+[languages.ru]
+contentDir = "content/ru"
+languageName = "Русский (Russian)"
+title = "Глоссарий Cloud Native"
+weight = 10
+[languages.ru.params]
+description = "Глоссарий Cloud Native — справочник по общим терминам, имеющим отношение к нативным облачным приложениям и технологиям. Разрабатывается фондом CNCF."
+
 [languages.zh-cn]
 contentDir = "content/zh-cn"
 languageName = "简体中文 (Simplified Chinese)"
 title = "Cloud Native(云原生) Glossary"
-weight = 10
+weight = 11
 [languages.zh-cn.params]
 description = "CNCF 云原生 Glossary 项目旨在用作讨论云原生应用程序时常用术语的参考"
 
 [languages.es]
 contentDir = "content/es"
 languageName = "Español (Spanish)"
 title = "Cloud Native Glosario"
-weight = 11
+weight = 12
 [languages.es.params]
 description = "El proyecto de CNCF Cloud Native Glosario pretende ser usado como una referencia para los terminos comunes usados cuando se habla acerca de las aplicaciones nativas para la nube."
 
 [languages.zh-tw]
 contentDir = "content/zh-tw"
 languageName = "繁體中文 (Traditional Chinese)"
 title = "Cloud Native(雲端原生) Glossary"
-weight = 12
+weight = 13
 [languages.zh-tw.params]
 description = "CNCF 雲端原生 Glossary 專案旨在用作討論雲端原生應用程式時常用術語的參考"
 
 [languages.tr]
 title = "Cloud Native Sözlüğü"
 languageName ="Türkçe (Turkish)"
 contentDir = "content/tr"
-weight = 13
+weight = 14
 [languages.tr.params]
 description = "CNCF Cloud Native Sözlüğü projesi, cloud native uygulamalardan bahsederken kullanılan yaygın terimler için bir referans olarak kullanılmak üzere tasarlanmıştır."
 
 [languages.ur]
 contentDir = "content/ur"
 languageName = "اردو (Urdu)"
 title = "کلاؤڈ کی مقامی لغت"
-weight = 14
+weight = 15
 [languages.ur.params]
 description = "CNCF کلاؤڈ کی مقامی لغت کا مقصد کلاؤڈ مقامی ایپلی کیشنز کے بارے میں بات کرتے وقت استعمال ہونے والی عام اصطلاحات کے حوالے کے طور پر استعمال کرنا ہے۔"
 
@@ -226,7 +234,7 @@ github_repo = "https://github.com/cncf/glossary"
 github_branch = "main"
 
 # Google Custom Search Engine ID. Remove or comment out to disable search.
-gcs_engine_id = "eda0239a7d3fd0d90"
+# gcs_engine_id = "eda0239a7d3fd0d90"
 
 # Enable Algolia DocSearch
 algolia_docsearch = false

content/de/search.md

@@ -0,0 +1,4 @@
+---
+title: Search Results
+layout: search
+---

content/en/application-programming-interface.md

@@ -21,4 +21,4 @@ Without a shared framework, it is challenging for applications to [scale](/scala
 
 APIs allow computer programs or applications to interact and share information in a defined and understandable manner. 
 They are the building blocks for modern applications and they provide developers with a way to integrate applications together. 
-Whenever you hear about [microservices](/microservices/) working together, you can infer that they interact via an API. 
+Whenever you hear about [microservices](/microservices-architecture/) working together, you can infer that they interact via an API. 

content/en/chaos-engineering.md

@@ -15,7 +15,7 @@ techniques to increase product resiliency and [reliability](/reliability/).
 A system's ability to tolerate failures while ensuring adequate service quality is 
 typically a software development requirement. 
 There are several aspects involved that could lead to outages of an application, 
-like infrastructure, platform or other moving parts of a ([microservice](/microservices/)-based) application. 
+like infrastructure, platform or other moving parts of a ([microservice](/microservices-architecture/)-based) application. 
 High-frequency deployment of new features to the production environment can 
 result in a high probability of downtime and a critical incident 
 — with considerable consequences to the business.

content/en/devops.md

@@ -11,7 +11,7 @@ DevOps calls for groups of engineers that work on small components (versus an en
 
 ## Problem it addresses
 
-Traditionally, in complex organizations with [tightly-coupled](/tightly-coupled-architectures/) [monolithic apps](/monolithic-apps/), 
+Traditionally, in complex organizations with [tightly-coupled](/tightly-coupled-architecture/) [monolithic apps](/monolithic-apps/), 
 work was generally fragmented between multiple groups. 
 This led to numerous handoffs and long lead times. 
 Each time a component or update was ready, it was placed in a queue for the next team. 

content/en/distributed-apps.md

@@ -6,7 +6,7 @@ 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/) 
+Distributed applications are usually composed of individual [microservices](/microservices-architecture/) 
 that handle different concerns within the broader application. 
 In a cloud native environment, the individual components typically run as [containers](/container/) on a [cluster](/cluster/). 
 

content/en/firewall.md

@@ -13,7 +13,7 @@ Firewalls can be hardware, software, or a combination of the two.
 
 By default, a network will allow anyone to enter and depart as long as they follow the network's routing rules. 
 Because of this default behavior, securing a network is challenging. 
-For example, in a [microservices](/microservices/)-based banking app, the services communicate with one another 
+For example, in a [microservices](/microservices-architecture/)-based banking app, the services communicate with one another 
 by transmitting highly sensitive financial data through their network. 
 A malicious actor may infiltrate the network, intercept communication, and do damage if there was no firewall in place.
 

content/en/function-as-a-service.md

@@ -5,30 +5,24 @@ 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 
-typically associated with building and launching [microservices](/microservices/) applications. 
-With FaaS, users manage only functions and data while the cloud provider manages the application. 
-This allows developers to get the functions they need without paying for services when code isn’t running.  
+Function as a Service (FaaS) is a cloud computing model that provides a platform for executing event-triggered functions, allowing for automatic scaling without manual intervention.
+At its essence, FaaS enables the deployment of individual functions that are activated by specific events, operate on a short-term basis, and then shut down, ensuring resources are not wasted.
+This model supports an [autoscaling](/auto-scaling/) feature, enabling a function instance to be initiated per request and terminated post-execution, emphasizing its stateless nature.
+Consequently, FaaS platforms can implement a true pay-as-you-go billing approach, eliminating costs when functions are dormant, distinguishing it from other models like [Platform as a Service (PaaS)](/platform-as-a-service/), which require continuous resource availability.
 
 ## Problem it addresses
 
-In a traditional on-premises scenario, a business manages and maintains its own data center. 
-The business must invest in servers, storage, software, and other technologies 
-and potentially hire an IT staff or contractors to purchase, manage, and upgrade all the equipment and licenses. 
-The data center has to be built to meet peak demand, even when workloads decline and those resources stand idle. 
-Conversely, if the business grows quickly, the IT department might struggle to keep up. 
-Under a standard [Infrastructure-as-a-Service (IaaS)](/infrastructure-as-a-service/) cloud computing model, 
-users pre-purchase capacity units, meaning you pay a public cloud provider for always-on server components to run your apps. 
-It’s the user’s responsibility to scale up server capacity during times of high demand 
-and scale down when that capacity is no longer needed. 
-The cloud infrastructure necessary to run an app is active even when the app isn’t being used.
+Traditionally, businesses have relied on maintaining on-premises data centers, necessitating substantial investment in hardware, software, and personnel.
+This setup demands resources to be scaled to peak demand, resulting in underutilized assets during downtime.
+Moreover, rapid business growth can overwhelm IT capabilities, leading to operational inefficiencies.
+In contrast, [Infrastructure-as-a-Service (IaaS)](/infrastructure-as-a-service/) models, while offering cloud-based solutions, still place the onus of scaling resources on the user, requiring payment for continuous server availability irrespective of actual usage.
 
 ## How it helps
 
-FaaS gives developers an [abstraction](/abstraction/) for running web applications in response to events without managing servers. 
-For example, uploading a file could trigger custom code that transcodes the file into various formats. 
-FaaS infrastructure will auto-scale the code for heavy use, 
-and the developer does not have to spend any time or resources building the code for [scalability](/scalability/). 
-Billing is based on computation time alone, which means businesses do not have to pay when the functions are not in use.
+FaaS gives developers an [abstraction](/abstraction/) for running web applications in response to events, eliminating the need to manage server infrastructure.
+For example, an action such as uploading a file could trigger custom code that transcodes the file into various formats.
+The FaaS infrastructure automatically adjusts resources to match demand, freeing developers from the complexities of coding for [scalability](/scalability/).
+Charges apply solely for the duration of computation, ensuring no costs accrue when functions are inactive.
+
+For more information, refer to the [Serverless](/serverless/) glossary entry.
+Although "serverless" and "FaaS" are often used as interchangeable terms, they embody distinct concepts.

content/en/load-balancer.md

@@ -6,7 +6,7 @@ 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/). 
+Take a [microservice](/microservices-architecture/) 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.
 Load balancers can be software or hardware-based.
 

content/en/loosely-coupled-architecture.md

@@ -8,7 +8,7 @@ tags: ["fundamental", "architecture", "property"]
 Loosely coupled architecture is an architectural style 
 where the individual components of an application are built independently from one another 
 (the opposite paradigm of [tightly coupled architectures](/tightly-coupled-architectures/)). 
-Each component, sometimes referred to as a [microservice](/microservices/), is built to perform a specific function 
+Each component, sometimes referred to as a [microservice](/microservices-architecture/), is built to perform a specific function 
 in a way that can be used by any number of other services. 
 This pattern is generally slower to implement than tightly coupled architecture 
 but has a number of benefits, particularly as applications scale.

content/en/monolithic-apps.md

@@ -13,7 +13,7 @@ the likelihood of conflicting changes and the need for interpersonal communicati
 
 ## Problem it Addresses
 
-Devolving an application into [microservices](/microservices/) increases its operational overhead 
+Devolving an application into [microservices](/microservices-architecture/) increases its operational overhead 
 — there are more things to test, deploy, and keep running. 
 Early in a product’s lifecycle, it may be advantageous to defer this complexity and build a monolithic application 
 until the product is determined successful.

content/en/mutual-transport-layer-security.md

@@ -11,7 +11,7 @@ instead of validating the identity of just one connection, both sides are valida
 
 ## Problem it addresses
 
-[Microservices](/microservices/) communicate over a network and, 
+[Microservices](/microservices-architecture/) communicate over a network and, 
 just like your wifi network, communication in transit over that network can be hacked. 
 mTLS ensures that no unauthorized party can listen in on or impersonate legitimate requests.
 

content/en/observability.md

@@ -9,7 +9,7 @@ Observability is a system property that defines the degree to which the system c
 It allows users to understand a system's state from these external outputs and take (corrective) action.
 
 Computer systems are measured by observing low-level signals such as CPU time, memory, disk space, and higher-level and business signals, including API response times, errors, transactions per second, etc.
-These observable systems are **observed** (or monitored) through specialized tools, so-called observability tools. A list of these tools can be viewed in the [Cloud Native Landscape's observability section](https://landscape.cncf.io/card-mode?category=observability-and-analysis&grouping=category).
+These observable systems are **observed** (or monitored) through specialized tools, so-called observability tools. A list of these tools can be viewed in the [Cloud Native Landscape's observability section](https://landscape.cncf.io/?group=projects-and-products&view-mode=card#observability-and-analysis--observability).
 
 Observable systems yield meaningful, actionable data to their operators, allowing them to achieve favorable outcomes (faster incident response, increased developer productivity) and less toil and downtime.
 

content/en/platform-as-a-service.md

@@ -11,7 +11,7 @@ Heroku, Cloud Foundry, App Engine are examples of PaaS offerings.
 
 ## Problem it addresses
 
-To take advantage of cloud native patterns like [microservices](/microservices/) or [distributed applications](/distributed-apps/), 
+To take advantage of cloud native patterns like [microservices](/microservices-architecture/) or [distributed applications](/distributed-apps/), 
 operations teams and developers need to be able to offload a significant amount of operations and maintenance work. 
 These include tasks like provisioning infrastructure, 
 handling [service discovery](/service-discovery/) and load balancing, and [scaling](/scalability/) applications.