top of page

Guidewire Cloud Scaling: A Step-by-Step Guide

  • May 8
  • 3 min read

In today's environment, the pressure on modern businesses to ensure application performance is both failover-capable and adaptable to their users' demands is ever-increasing. In an effort to run complex workloads in the cloud, companies have moved from a limited-resource environment (i.e., physical resources) to an unlimited or infinite resource environment (i.e., cloud resources). To do this, organizations need to successfully manage this transition using Guidewire Training or similar approaches to ensure enterprise-class software is able to work seamlessly with an automated infrastructure.

Guidewire training provides IT professionals and insurance professionals with a path towards mastering the Guidewire InsuranceSuite. The Guidewire InsuranceSuite is industry-standard software that is used by P&C insurance carriers as a single platform for all of their business processes from issuing a policy through claims processing and everything in between. To achieve optimal performance while keeping an economically sustainable operation, all businesses must understand the triggers that require resources to be adjusted for optimum performance.


The Essential Elements of Scaling

The system will not be affected by sudden and very momentary spikes. It will instead evaluate the timeframe of all changes to see if a load is shifting in a consistent way over that time period before assessing how quickly it should respond to make sure that an appropriate response is provided.


The Mechanics of Scaling up vs. Scaling Down

When scaling, you will add or take away (scale up or scale down) from the number of active instances according to your current level of activity. However, the accepted rationale for adding resources is quite different from the rationale for removing those same resources. 


Direction

Trigger Criteria

Operational Rationale

Scaling Up

High CPU usage, an increasing number of requests, and slow performance

Action taken when these conditions occur means that your current configuration is out of scale.

Scaling Down

Low CPU, decreasing number of requests, and steady decrease in traffic

A gradual means is implemented to obtain consistency.

 

Important Configuration Factors

A high level of technical expertise is frequently a primary focus for individuals who are interested in obtaining Guidewire Certification.

In addition, many organizations will move beyond traditional system metrics and use “custom metrics” to allow for scaling based on their business-specific data, such as pending background jobs or certain financial numbers, as opposed to only raw CPU performance. Many professionals see the value in participating in Guidewire Functional Training so that they better understand how these business processes will translate into their technical requirements.


Common Issues You May Experience

Not all scaling efforts go as planned. This will usually occur when incorrect settings have been applied to the configuration. Some common issues that result from the incorrect settings include scaling too late, scaling too soon, or creating too many instances. Another common issue is “cold start,” where a new instance requires a period of time to properly initialize. Examining these types of issues within real environments, it will allow individuals to make more informed decisions during actual operational conditions. 


Conclusion

Scaling Google Cloud operates in an uncomplicated and methodical manner. While Google Cloud consistently monitors your application throughout its entire lifecycle, it waits until it determines the appropriate conditions exist before initiating any scaling operation. There is no rushing on their part; they will wait until they can determine whether the observed load change is indeed real prior to initiating any type of operation.

Scaling up will take place when the observed load is increasing, and scaling down will take place after the observed load has decreased over an extended period of time. When properly configured, timeouts, maximum concurrent processes, and cooldown periods will greatly influence the overall scaling mechanism of your application. The basic objective behind Guidewire training and education is to develop a thoughtful approach to managing your resources and ensuring your enterprise applications are scalable and cost-effective, regardless of the amount of traffic generated. 


 
 
 

Comments


bottom of page