Twoja przeglądarka nie obsługuje JavaScript.
Nie uzyskasz więc dostępu do niektórych jej funkcjonalności.
Aby w pełni cieszyć się używaniem strony Intratel
włącz obsługę JavaScript w swojej przeglądarce.

Effective scalling - with automation only

One of the main reasons why it is worth moving your enterprise resources to the cloud is the ability of scaling resources. For many of these enterprises, scaling means the achievement of all these features regarded with economies of scale, managing large collections of computing resources in the most effective and efficient manner. With this economy, the computing resources will be available to business end-users in a much lower cost than they would be in traditional infrastructure.  


Scaling in the cloud computing infrastructure is achieved in two ways. Scaling up means adding instances or virtual machines to the distributed systems, which practically means providing virtual machine with additional memory or CPUs. To be able to scale up quickly and easily, a good provider should have a management console or APIs. On the other hand, there should be the ability to quickly reduce the resources in use in order to avoid overcharging for redundant resources in the cloud infrastructure. Console or API should provide the ability to quickly scale the instance by adding memory or processors that are able to process workloads on a single server.  


The main difference between using physical hardware and placing cloud resources at the disposal of corporate end users, is time. In case of the cloud, time is counted in hours and minutes, which means that it is necessary to know in advance when resources will be needed, and when can be reduced or waived.      

Although the cloud service provider should provide the ability to scale, it is important that a company's IT department had control over scaling. Orchestration and automation systems are extremely important, and if possible, these should be included in workload SLAs, so that the use of services during peak periods does not affect the end-user experience. What is expected primarily from the process of automation, is the level of service use monitoring, so that bills issued by a service provider would not raise any doubts.  


As with traditional infrastructure, firms that scale up servers or resources in the cloud are permanently vulnerable to making a mistake of purchasing high values for a peak period and leave them unused after that time. And this is the best example to explain the importance of the automation process in cloud services. The cloud gives you the ability to pay for services in a "pay as you use" model by matching expected workloads and required capacity. Such automation is essential to ensure that the capacity value is adequate to the needs of a workload, effectively eliminating unnecessary costs of unused resources. Therefore, corporate users should carefully use the resources they need, and remember to turn off the scaling up of the resources they no longer need.      


Scaling the cloud within an organization or business should be run according to certain rules. The gives three basic ones:      

Planning – estimate resources values that will be needed. It's about defining what in a particular industry and business peak periods mean, and when exactly the periods start.

The second thing is testing and verification how a cloud may behave during peak periods. There are software services, as well as servers and products to simulate sudden increase in cloud load balancing for any organization for testing.

Thirdly – disaster recovery plan for the event of unexpected incidents, as part of an efficient scaling strategy is identification and implementation of options for the time when scaling will not be possible.,1