You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/content/en/contribute/_index.md b/content/en/contribute/_index.md
index 3e4eb81..59ef0ba 100644
--- a/content/en/contribute/_index.md+++ b/content/en/contribute/_index.md@@ -62,9 +62,7 @@ Read our [Style Guide](/style-guide/) to understand our guidelines for formattin
## Join the Glossary community! {#join-the-glossary-community}
-If you want to contribute regularly, consider joining our monthly Glossary Working Group meetings. -You can find the meeting details in the [CNCF calendar](https://www.cncf.io/calendar/). -You can also connect with the maintainers and fellow contributors in our [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel on the CNCF Slack +Connect with the maintainers and fellow contributors in our [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel on the CNCF Slack
— we'd love to meet you!
## Work on an existing issue {#work-on-an-existing-issue}
@@ -84,7 +82,7 @@ Once you select a term to work on, comment on the issue.
Additionally, notify the maintainers on the [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel of the CNCF Slack workspace and
-tag _@iamnoah_, _@nate-double-u_, _@Seokho Son_, _@Jihoon Seo_, and/or _@castrojo_ to be sure they don't miss it.+tag _@iamnoah_, _@nate-double-u_, _@Seokho Son_, _@Jihoon Seo_ and/or _@Junya Okabe_ to be sure they don't miss it.
For the next steps, please refer to the [Submitting a new term (creating a PR)](#submitting-a-new-term) section.
@@ -125,7 +123,7 @@ Next, the maintainers will triage the issue.
That means they will assess if the term should be part of the Glossary.
Not every term will be admitted. To be included in the Glossary, they should be established and widely-used cloud native concepts.
-Please let the maintainers know that you've proposed a new term on Slack and tag _@iamnoah_, _@nate-double-u_, _@Seokho Son_, _@Jihoon Seo_, and/or _@castrojo_ so that they don't miss it.+Please let the maintainers know that you've proposed a new term on Slack and tag _@iamnoah_, _@nate-double-u_, _@Seokho Son_, _@Jihoon Seo_ and/or _@Junya Okabe_ so that they don't miss it.
If you want to work on the definition, let the maintainers know and they'll assign it to you.
### Submitting a new term (creating a PR) {#submitting-a-new-term}
diff --git a/content/en/_index.md b/content/en/_index.md
index 4465bc8..b192cb0 100755
--- a/content/en/_index.md+++ b/content/en/_index.md@@ -1,53 +1,54 @@
---
-title: "Cloud Native Glossary"+title: Cloud Native Glossary
status: Completed
---
# Cloud Native Glossary
-The Cloud Native Glossary aims to make the cloud native space — which is notorious for its complexity — simpler for people by making it easier to understand, -not only for technologists but also for people on the business side. -To achieve that, we focus on simplicity (e.g., simple language free from buzzwords, examples anyone using technology can relate to, leaving unnecessary details out). -The Glossary is a project led by the CNCF Business Value Subcommittee (BVS). +The Cloud Native Glossary aims to make the cloud native space — which is notorious for its complexity — simpler for people by making it easier to understand,+not only for technologists but also for people on the business side.+To achieve that, we focus on simplicity (e.g., simple language free from buzzwords, examples anyone using technology can relate to, leaving unnecessary details out).+The Glossary is a project led by the CNCF Business Value Subcommittee (BVS).
<p><img class="mt-3" src="/images/homepage/kubecon.jpg" alt="People watching a Kubecon presentation"></p>
## Contributing
-Everybody is invited to suggest changes, additions, and improvements to the Cloud Native Glossary. -We employ a community-driven process governed by the CNCF to develop and improve upon this shared lexicon. -This Glossary provides a vendor-neutral platform to organize a shared vocabulary around cloud native technologies. +Everybody is invited to suggest changes, additions, and improvements to the Cloud Native Glossary.+We employ a community-driven process governed by the CNCF to develop and improve upon this shared lexicon.+This Glossary provides a vendor-neutral platform to organize a shared vocabulary around cloud native technologies.
Contributions are welcome from all participants who abide by the project's purpose and charter.
Anyone wishing to contribute may submit a GitHub issue or create a pull request.
-Please ensure you follow the [Style Guide](/style-guide/), read the [How To Contribute](/contribute/) doc, join the [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf) workspace, and join the [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel.+Please ensure you follow the [Style Guide](/style-guide/), read the [How To Contribute](/contribute/) doc, join the [CNCF Slack](https://slack.cncf.io) workspace, and join the [#glossary](https://cloud-native.slack.com/archives/C02TX20MQBB) channel.
There is also a [#glossary-localizations](https://cloud-native.slack.com/archives/C02N2RGFXDF) channel for those who want to help translate the glossary into their native language.
## Acknowledgements
-The Cloud Native Glossary was initiated by the CNCF Marketing Committee (Business Value Subcommittee) and includes contributions from -[Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/), -[Chris Aniszczyk](https://www.linkedin.com/in/caniszczyk/), -[Daniel Jones](https://www.linkedin.com/in/danieljoneseb/?originalSubdomain=uk), -[Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), -[Katelin Ramer](https://www.linkedin.com/in/katelinramer/), -[Mike Foster](https://www.linkedin.com/in/mfosterche/?originalSubdomain=ca), -and many more contributors. +The Cloud Native Glossary was initiated by the CNCF Marketing Committee (Business Value Subcommittee) and includes contributions from+[Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/),+[Chris Aniszczyk](https://www.linkedin.com/in/caniszczyk/),+[Daniel Jones](https://www.linkedin.com/in/danieljoneseb/?originalSubdomain=uk),+[Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/),+[Katelin Ramer](https://www.linkedin.com/in/katelinramer/),+[Mike Foster](https://www.linkedin.com/in/mfosterche/?originalSubdomain=ca),+and many more contributors.
For a complete contributor list, please refer to [this GitHub page](https://github.com/cncf/glossary/graphs/contributors).
-The Glossary is maintained by +The Glossary is maintained by
[Seokho Son](https://www.linkedin.com/in/seokho-son/),
-[Noah Ispas](https://www.linkedin.com/in/noah-ispas-0665b42a/), +[Noah Ispas](https://www.linkedin.com/in/noah-ispas-0665b42a/),
[Jihoon Seo](https://www.linkedin.com/in/jihoon-seo/),
-[Nate W.](https://www.linkedin.com/in/nate-double-u/),-and [Jorge Castro](https://www.linkedin.com/in/jorge-castro2112/).+[Nate W.](https://www.linkedin.com/in/nate-double-u/)+and [Junya Okabe](https://www.linkedin.com/in/junya-okabe/).
[Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/),
-and [Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/)+[Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/) and+[Jorge Castro](https://www.linkedin.com/in/jorge-castro2112/)
are Emeritus Maintainers, and we are deeply grateful
for their invaluable contributions over the years.
## License
-All code contributions are under the Apache 2.0 license. +All code contributions are under the Apache 2.0 license.
Documentation is distributed under CC BY 4.0.
diff --git a/content/en/container.md b/content/en/container.md
index 6cb69fe..28a2d90 100644
--- a/content/en/container.md+++ b/content/en/container.md@@ -28,3 +28,5 @@ There are limitations, however.
Since containers share the same operating system, processes can be considered less secure than alternatives.
Containers also require limits on the shared resources.
To guarantee resources, administrators must constrain and limit memory and CPU usage so that other applications do not perform poorly.
++{{% sign-language-section meUtsFU7ndo %}}
diff --git a/content/en/cloud-computing.md b/content/en/cloud-computing.md
index f92f709..36eb04f 100644
--- a/content/en/cloud-computing.md+++ b/content/en/cloud-computing.md@@ -5,7 +5,7 @@ category: concept
tags: ["infrastructure", "fundamental", ""]
---
-Cloud computing offers CPU power, storage, and network capabilities over the internet, +Cloud computing offers CPU power, storage, and network capabilities,
enabling scalable and flexible access to resources across global data centers.
It spans private clouds, dedicated to single organizations for security and control,
and public clouds, open for widespread use, optimizing cost and scalability.
diff --git a/content/en/virtual-machine.md b/content/en/virtual-machine.md
index b819a50..c29385a 100644
--- a/content/en/virtual-machine.md+++ b/content/en/virtual-machine.md@@ -31,4 +31,6 @@ VMs allow you to use your existing physical hardware resources better
by placing multiple virtual machines on a single physical machine.
Not bound to a particular physical machine, VMs are also more resilient than physical machines.
When a physical machine needs to go offline,
-the VMs running on it can be moved to another machine with little to no downtime.
\ No newline at end of file
+the VMs running on it can be moved to another machine with little to no downtime.++{{% sign-language-section Fq-kda8kIHg %}}
diff --git a/content/en/reliability.md b/content/en/reliability.md
index c1ab8a5..c8f2908 100644
--- a/content/en/reliability.md+++ b/content/en/reliability.md@@ -9,3 +9,5 @@ From a cloud native perspective, reliability refers to how well a system respond
If we have a [distributed system](/distributed-systems/) that keeps working as infrastructure changes and individual components fail, it is reliable.
On the other hand, if it fails easily and operators need to intervene manually to keep it running, it is unreliable.
The goal of [cloud native applications](/cloud-native-apps/) is to build inherently reliable systems.
++{{% sign-language-section pQluo2FG2eA %}}
diff --git a/content/en/serverless.md b/content/en/serverless.md
index 17a824a..bb46da1 100644
--- a/content/en/serverless.md+++ b/content/en/serverless.md@@ -9,12 +9,12 @@ tags: ["architecture", "", ""]
Serverless Computing [abstracts](/abstraction/) servers away from the user.
Operational management falls to the service provider, including handling physical machines and VM provisioning.
Service providers can be public cloud entities or internal IT departments serving their development teams.
-These providers offer user interfaces such as SDKs, CLIs, or OCI-compliant runtimes, focusing on code and deployment tasks.+These providers offer user interfaces such as SDKs, CLIs, or OCI-compliant [runtimes](/runtime/), focusing on code and deployment tasks.
Charges are based on a pay-per-use model.
[Scaling](/scalability/) and resource provisioning for computing, storage, or networking are automatically adjusted based on application demand without user intervention.
A serverless platform provider consolidates resources to serve multiple users on a single physical machine, ensuring isolation through virtualization, especially with [VMs](/virtual-machine/).
-Serverless is a comprehensive term encompassing services with these attributes, extending from [Platform-as-a-Service (PaaS)](/platform-as-a-service/) to [Software-as-a-Service (SaaS)](/software-as-a-service/).+Serverless is a comprehensive term encompassing services with these attributes, extending from Platform-as-a-Service (PaaS) to Software-as-a-Service (SaaS).
## Problem it addresses
@@ -30,3 +30,5 @@ Tasks such as operating system maintenance, security updates, load balancing, ca
Refer to the [Function-as-a-Service (FaaS)](/function-as-a-service/) glossary entry for more information.
Although "serverless" and "FaaS" are often used as interchangeable terms, they embody distinct concepts.
++{{% sign-language-section rbyBgXqCN2k %}}
diff --git a/content/en/horizontal-scaling.md b/content/en/horizontal-scaling.md
index 99b1f71..40f1abd 100644
--- a/content/en/horizontal-scaling.md+++ b/content/en/horizontal-scaling.md@@ -7,10 +7,11 @@ 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, -scaling it horizontally means doing so by adding 4 x 4GB RAM rather than switching to a 16GB RAM system.+Let's say, we have a system of 4GB RAM and want to increase its capacity to 16GB RAM. +Scaling it horizontally means doing so by adding 3 nodes x 4GB RAM rather than switching to +a 16GB RAM system.-This approach enhances the performance of an application by adding new instances, or [nodes](/nodes/), +This approach enhances the performance of an application by adding new instances, or nodes,
to better distribute the workload.
In simple words, it aims to decrease the server's load
rather than expanding capacity of the individual server.
diff --git a/content/en/style-guide/_index.md b/content/en/style-guide/_index.md
index bab8303..6587768 100644
--- a/content/en/style-guide/_index.md+++ b/content/en/style-guide/_index.md@@ -26,7 +26,7 @@ Additionally, it follows the following rules:
## Audience
The Glossary is written for technical *and* non-technical audiences.
-Please explain definitions in simple terms, and don’t assume technical knowledge. More about this is below in [Definition](#definition).+Please explain definitions in simple terms, and don’t assume technical knowledge. More about this is below in [Definition](#definition) and the [Sign Language Style Guide](#sign-language-style-guide).
## Minimum viable definition
@@ -164,6 +164,8 @@ Additionally, it uses a real-world example comparing network challenges in a mic
to wifi problems (something anyone using a laptop can understand).
Where possible, try to make that connection.
++
#### Start with a Google or Word doc
We recommend starting with a Google or Word doc, letting it sit for a few days, and revisiting it.
@@ -176,9 +178,93 @@ More about that in the [How To Contribute](/contribute/) doc.
Before getting started, please read some published Glossary terms
to get a feeling for the level of detail and difficulty and when examples are appropriate.
+++## Sign Language Video Style Guide {#sign-language-style-guide}++If you are contributing a sign language video, please follow these guidelines to ensure our videos are clear, informative, and accessible to a wide audience (Including hearing community members).+++### Technical equipment++All you need is a high-resolution camera and a stand. A modern smartphone should be enough.+++### Recording Setup++++* **Lighting:** Use frontal lighting to ensure your face and hands are well-lit.+++* **Background:** Record in front of a flat, solid background to avoid distractions from the signing. Ensure no distracting decorations are included.+++* **Dress Code:** Wear a solid, single-color top (no prints) that contrasts with your skin tone.+++* **Camera Position:** Ensure that your head to your elbows are visible on the screen, and position the camera at eye level. The camera should be perpendicular to the background so that it appears straight, not slanted.+++* **Signing Space:** Use as much space as possible to ensure you have full signing space while sitting or standing.+++* **Sound:** Mute the microphone (input audio) when possible to avoid involuntary background noise.++### Signing++++* **Clarity and Accuracy:** Record the sign twice from a frontal orientation, signing slowly enough for non-signers to see and mimic it. Demonstrating signs from the side is unnecessary unless it adds clarity. +++* **Facial Expression:** Use relaxed or neutral facial expressions. Mouthing or making grimaces is strongly discouraged. Maintain eye contact with the camera if possible.+++* **Frequency:** Only one sign is needed for each video, as playback can be looped. Repeating the sign in a video is unnecessary.+++* **Duration:** The total length of the video should not exceed 7 seconds.+++* **Fingerspelling:** Use sign language for the word as much as possible. Fingerspelling is the last resort, commonly reserved for abbreviated or short words.+++* **Posture:** Maintain a frontal orientation with eyes facing the camera while signing. Demonstrating signs using side orientation is unnecessary. When at rest, arms should be down with hands relaxed.++### Tips++++* **Save storage space:** Please remember the shorter the video, the smaller the file would be. The faster it will upload.+++* **Mistakes are good:** Keep the recording running while making several attempts. It is more likely you will find a good clip in between tries, and you can trim the unwanted parts. This is more efficient than making multiple recordings with one sign attempt in each.+++* **Videos Examples:** Please refer to the [CNCF Glossary: Cloud Native Signs](https://www.youtube.com/playlist?list=PLj6h78yzYM2PDlYnmfpRfKgcgBMb34kb5) playlist for examples. ++### Post-Production++++* **Editing:** If necessary, trim the beginning and the end of the video.+++* **Label:** At a minimum, the filename of the video should contain the glossary term of the sign before uploading. For example, kubernetes.mp4.+++* **Audio:** Remove the audio track entirely, if possible.+++* **Upload:** Share the video on the #glossary-sign-language Slack channel and ask for feedback. If approved, the Sign Language Glossary leads will help you upload the video to the CNCF Playlist. Please do not upload the videos to your personal YouTube as YouTube could potentially remove duplicate videos from all accounts using the same videos (to prevent monetizing abuse) as CNCF uses YouTube to upload final videos. +++* **Video upload on CNCF playlist:** Share the video on the #glossary-sign-language Slack channel and ask for feedback. If approved, the Sign Language Glossary leads will help you upload the video to the CNCF Playlist. +
## The review process: What to expect
-Please note that we are currently only three maintainers doing this in their spare time. +Please note that we are currently only a handfull maintainers doing this in their spare time.
Occasionally, we'll be able to review terms quickly; on other occasions, it may take some time—we appreciate your patience.
If you have any questions, please contact us in the #glossary Slack channel
(for where and how to find it, please refer to our [How To Contribute](/contribute/) doc).
diff --git a/content/en/contributor-ladder/_index.md b/content/en/contributor-ladder/_index.md
index f3bb984..1deb198 100644
--- a/content/en/contributor-ladder/_index.md+++ b/content/en/contributor-ladder/_index.md@@ -31,7 +31,10 @@ Please refer to the [How to Contribute](/contribute/) and [Style Guide](/style-g
## 2. Approvers
Approvers provide feedback on PRs and approve them. Any active contributor can become an approver (see [Becoming an approver](#becoming-an-approver)).
-The Glossary differentiates between two approvers: (1) approvers for the English Glossary and (2) approvers for localization teams.+The Glossary differentiates between two approvers: ++1. approvers for the English Glossary and +2. approvers for localization teams.
Glossary approvers are expected to:
@@ -44,7 +47,7 @@ If an approver is no longer interested in or cannot perform the above duties, th
### English Glossary Approvers
-There are three types of approvers:+There are three types of English Glossary approvers:
1) Approvers with a strong technical background,
2) Approvers with solid writing skills,
@@ -65,7 +68,6 @@ Any localization approver can also become an approver for the English Glossary i
### Becoming an Approver
Approver candidates should have a proven track record of submitting high-quality PRs and helping others get their PRs in a mergeable state.
-If their timezone permits, they should also regularly attend the [Glossary Working Group meetings](https://www.cncf.io/calendar/).
To become an approver, start by expressing interest to existing maintainers.
Existing maintainers will then ask you to demonstrate the qualifications above by contributing PRs, doing reviews, and doing other such tasks under their guidance.
@@ -80,40 +82,23 @@ There are certain expectations for maintainers, including:
- Be an active and responsive approver (see above),
- Help maintain the repository, including site configuration, permission, issue-template, GitHub workflow, among others,
- Monitor the Glossary Slack channels and help out whenever possible,
-- Regularly attend the [Glossary Working Group meetings](https://www.cncf.io/calendar/) (if timezone permits)--If a maintainer is no longer interested in or cannot perform the duties listed above, they should move themselves to emeritus status.
### Becoming a Maintainer
Maintainers should have a proven track record of being successful approvers and submitting high-quality PRs.
-If their timezone permits, they should also regularly attend the Glossary Working Group meetings.
To become a maintainer, start by expressing interest to existing maintainers.
Existing maintainers will then ask you to demonstrate the qualifications above by contributing PRs, doing reviews, and doing other such tasks under their guidance.
After some time of working together, maintainers will decide whether to grant maintainer status.
This decision will be based on demonstrated level of proficiency and responsiveness.
-## 4. Community Managers--Community managers help foster a welcoming and engaging community. Any community member can become a community manager. They are expected to:--- Welcome new members and ensure they get the information they need,-- Help answer questions from the community or identify someone who can help,-- Moderate conversations on Slack.--### Become a Community Manager--Anyone can become a Glossary community manager. -Community managers must have a solid understanding of the contribution and localization process and enjoy interacting and helping others. -To become a community manager, start by expressing interest to existing maintainers. -After an onboarding/trial period, maintainers will decide whether to grant community manager status based on performance. -
## Involuntary Removal
Involuntary removal of a contributor happens when responsibilities and requirements aren't met.
This may include repeated patterns of inactivity, extended periods of inactivity, and/or a violation of the code of conduct.
-This process is important because it protects the community and its deliverables while also opening up opportunities for new contributors to step in.+This process is important because it protects the community and its deliverables while also opening up opportunities for new contributors to step in. ++The grace period will be something between 15-30 days where the maintainers will actively try to reactivate an unresponsive contributor. In case of a localization team if an approver becomes unresponsive leading to a minority of nesseccary approvers, localization contributors will be asked to step up to become an approver.
## Stepping Down/Emeritus Process
@@ -122,4 +107,4 @@ moving to emeritus status (completely stepping away from the project).
## Stepping Back Into a Role
-If and when someone is available to step back into a previous contributor role, project leadership can arrange and consider this.+If and when someone is available to step back into a previous contributor role, the maintainers can arrange and consider this.
diff --git a/content/en/stateless-apps.md b/content/en/stateless-apps.md
index 6cf8647..c9f18cb 100644
--- a/content/en/stateless-apps.md+++ b/content/en/stateless-apps.md@@ -5,11 +5,10 @@
tags: ["fundamental", "application", "property"]
---
-Stateless applications process requests as if each request were the first it's ever been sent. -The app doesn't "remember" previous interactions or user session data. -Data from previous interactions is referred to as state, and since that data isn't stored anywhere, these apps are state*less*. +Stateless applications handle each request independently without remembering any previous interactions or user data.+Data from previous interactions is referred to as state since that data isn’t stored anywhere, these apps are state*less*.
Here's an example:
When you use a search engine, and that search is interrupted (e.g., the window is closed), those search results are lost.
You'll need to start all over.
-On the other hand, applications that process requests while considering previous interactions are called [stateful applications](/stateful-apps/).
\ No newline at end of file
+On the other hand, applications that process requests while considering previous interactions are called [stateful applications](/stateful-apps/).
diff --git a/content/en/service.md b/content/en/service.md
index d0edc8e..2406c43 100644
--- a/content/en/service.md+++ b/content/en/service.md@@ -10,3 +10,5 @@ In this definition, we'll focus on the more traditional one: service as in micro
How or even if services differ from microservices is nuanced and different people may have different opinions.
For a high-level definition, we'll treat them as the same.
Please refer to the [microservices](/microservices-architecture/) definition.
++{{% sign-language-section rE5OCe3upMo %}}
diff --git a/content/en/auto-scaling.md b/content/en/auto-scaling.md
index 2b76962..ad9e7e4 100644
--- a/content/en/auto-scaling.md+++ b/content/en/auto-scaling.md@@ -26,3 +26,5 @@ increasing the number of servers allowing for more video streaming and scaling b
* [Horizontal Scaling](/horizontal-scaling/)
* [Vertical Scaling](/vertical-scaling/)
++{{% sign-language-section cGONmC1smaM %}}
diff --git a/content/en/function-as-a-service.md b/content/en/function-as-a-service.md
index 6155011..7aabd91 100644
--- a/content/en/function-as-a-service.md+++ b/content/en/function-as-a-service.md@@ -5,14 +5,14 @@ category: Technology
tags: ["infrastructure", "", ""]
---
-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.+Function as a Service (FaaS) is a [cloud computing](/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.+This model supports an [autoscaling](/auto-scaling/) feature, enabling a function instance to be initiated per request and terminated post-execution, emphasizing its [stateless](/stateless-apps/) 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), which require continuous resource availability.
## Problem it addresses
-Traditionally, businesses have relied on maintaining on-premises data centers, necessitating substantial investment in hardware, software, and personnel.+Traditionally, businesses have relied on maintaining on-premises [data centers](/data-center/), 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.
@@ -23,6 +23,6 @@ FaaS gives developers an [abstraction](/abstraction/) for running web applicatio
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.
\ No newline at end of file
+Although "serverless" and "FaaS" are often used as interchangeable terms, they embody distinct concepts.
The end of report
The text was updated successfully, but these errors were encountered:
This is an issue to track and reflect updates of English content. Please, check the files below as they may have been improved.
NOTICE - The following outdated content should be resolved before the next L10n branch updates.
Files to check
Changes in each file
contribute/_index.md
Diff in detail
_index.md
Diff in detail
container.md
cloud-computing.md
virtual-machine.md
reliability.md
serverless.md
Diff in detail
horizontal-scaling.md
tightly-coupled-architectures.md
style-guide/_index.md
Diff in detail
contributor-ladder/_index.md
Diff in detail
stateless-apps.md
service.md
auto-scaling.md
function-as-a-service.md
Diff in detail
The end of report
The text was updated successfully, but these errors were encountered: