forked from kubernetes/website
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Autoscaling V1-ready (kubernetes#54)
- Loading branch information
Showing
1 changed file
with
7 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,16 @@ | ||
--- | ||
title: Autoscaling | ||
status: Feedback Appreciated | ||
status: Completed | ||
category: Concept | ||
--- | ||
## Autoscaling | ||
|
||
Applications require scaling in order to meet the fluctuating demand of their users. Autoscaling is an automated method for the scaling of said applications. The autoscaling process varies and can be configured to scale based on different metrics, such as memory or process time. | ||
### What it is | ||
Autoscaling simply means scaling in an automated fashion, typically, the scaling of computing resources. With an autoscaling system, resources are automatically added when needed and can scale to meet fluctuating user demands. The autoscaling process varies and is configurable to scale based on different metrics, such as memory or process time. Managed cloud services are typically associated with autoscaling functionality as there are more options and implementations available than most on-premise deployments. | ||
|
||
### Problem it Addresses | ||
Previously, infrastructure and applications were architected to consider peak system usage. This architecture meant that more resources were underutilized and inelastic to changing consumer demand. The inelasticity meant higher costs to the business and lost business from outages due to overdemand. | ||
|
||
By virtualizing and containerizing applications and their dependencies, they can scale according to their demand. Organizations can monitor their application demand and automatically scale them based on their needs to give the best user experience. | ||
### How it Helps | ||
By leveraging the cloud, virtualizing, and containerizing applications and their dependencies, organizations can build applications that scale according to user demands. They can monitor application demand and automatically scale them, providing an optimal user experience. Take the increase in viewership Netflix experiences every Friday evening. Autoscaling out means dynamically adding more resources: for example, increasing the number of servers allowing for more video streaming and scaling back once consumption has normalized. | ||
|