Scale out là gì
14:45, 20/10/2021
Modern applications are constantly changing, evolving with new requirements & exist in an environment with varying demands on resources. Scaling an application can appropriately size it to resource demands lớn ensure happy customers and reduce infrastructure costs. If you don’t know how to lớn scale efficiently, you are not just doing a disservice to lớn your application, you are putting unnecessary bít tất tay on your operations team. Manually trying lớn determine when to scale up or out is extremely difficult. If you buy more infrastructure khổng lồ accommodate your peak traffic, you could be overspending when load is not at peak. If you target your average load, spikes in traffic will impact your application performance và, when traffic drops, these resources will go unused.
Bạn đang xem: Scale out là gì
What is Scale up vs Scale out?
Scaling out, or horizontal scaling, contrasts khổng lồ scaling out, or vertical scaling. The idea of scaling cloud resources may be intuitive sầu. As your cloud workload changes it may be necessary lớn increase infrastructure to tư vấn increasing load or it may make sense to lớn decrease infrastructure when demvà is low. The “up or out” part is perhaps less intuitive sầu. Scaling out is adding more equivalently functional components in parallel to lớn spread out a load. This would be going from two load-balanced web server instances to lớn three instances. Scaling up, in contrast, is making a component larger or faster lớn handle a greater load. This would be moving your application lớn a virtual VPS (VM) with 2 CPU to one with 3 CPUs. For completeness, scaling down refers lớn decreasing your system resources, regardless of whether you were using the up or out approach.
Scale up
Resources such as CPU, network, và storage are common targets for scaling up. The goal is to increase the resources supporting your application to reach or maintain adequate performance. In a hardware-centric world, this might mean adding a larger hard drive to a computer for increased storage capađô thị. It might mean replacing the entire computer with a machine that has more CPU & a more performant network interface. If you are managing a non-cloud system, this scaling up process can take anywhere from weeks up to lớn months as you request, purchase, install, và finally deploy the new resources.
In a cloud system, the process should take seconds or minutes. A cloud system might still target hardware & that will be on the tens of minutes end of the time lớn scale range. But virtualized systems dominate cloud computing & some scaling actions, like increasing storage volume capađô thị or spinning up a new container lớn scale up a microservice can take seconds khổng lồ deploy. What is being scaled will not be that different. One may still shift applications to a larger VM or it may be as simple as allocating more capađô thị on an attached storage volume.
Regardless of whether you are dealing with virtual or hardware resources, the take-home page point is that you are moving from one smaller resource và scaling up to one larger, more performant resource.
Scale out
Scaling up makes sense when you have sầu an application that needs khổng lồ sit on a single machine. If you have an application that has a loosely coupled architecture, it becomes possible to lớn easily scale out by replicating resources.
Scaling out a microservices application can be as simple as spinning up a new container running a webVPS ứng dụng và adding it to the load balancer pool. When scaling out the idea is that it is possible khổng lồ add identical services to lớn a system lớn increase performance. Systems that support this mã sản phẩm also tolerate the removal of resources when the load decreases. This allows greater fluidity in scaling resource size in response to lớn changing conditions.
The incremental nature of the scale out model is of great benefit when considering cost management. Because components are identical, cost increments should be relatively predictable. Scaling out also provides greater responsiveness to changes in demand. Typically services can be rapidly added or removed khổng lồ best meet resource needs. This flexibility & speed effectively reduces spending by only using (& paying for) the resources needed at the time.
grumpygourmetusa.com can help you.
When it comes to how khổng lồ scale, there is a continuum of effort:
Reactive/Manual. You use metrics lớn evaluate resource use và manually calculate costs, using a tool like Kubecost. When you see the load grow or receive sầu a notification from your metrics service of a load threshold being crossed and reactively make an adjustment as a result. When it is decided that the system must be scaled, the process to do so is implemented manually.Manual/Semi-automated.Xem thêm: # Nhà Hướng Bắc Đặt Bếp Hướng Nào Tốt Theo Phong Thủy, Nhà Hướng Tây Đặt Bếp Hướng Nào
Your metrics system and infrastructure management system are linked. You continue to periodically evaluate costs based on feedback from your metrics system, check on current cloud provider costs, và then update your orchestration system (e.g. Kubernetes) lớn autoscale when specific load limits are reached.Fully Automated. You evaluate cost & performance goals proactively & automatically tune the system to lớn maintain desired limits using AI-driven software. This can be done using grumpygourmetusa.com.Scaling allows you to lớn meet your customer’s demands for quality service while minimizing the cost of providing that unique service. grumpygourmetusa.com works khổng lồ ensure your application is running efficiently & at the lowest cost possible. Moreover, we want lớn ensure you get the performance you need while spending the least amount of money lớn achieve it. grumpygourmetusa.com lets you focus on delivering the core values of your business by automating away the toil – the repetitive & manual tasks – associated with optimizing systems that are constantly changing. grumpygourmetusa.com leverages artificial intelligence & machine learning, particularly deep reinforcement learning, khổng lồ predict traffic spikes and resource requirements will accurately predict the best moment to lớn scale up or down, & seamlessly integrates with AWS tooling to automate the scaling process. No toil necessary. To find out how grumpygourmetusa.com can reduce your AWS spkết thúc, check out AWS does not Equal Cloud Optimization.
