Illustration figure with elastic arm

Elastic IT for insurers

An infrastructure that adapts to peak loads

First came the cloud, now we have the elastic cloud

As part of their digital transition, more and more insurers are turning to cloud computing to exploit the benefits of modern IT landscapes. In doing so, CIOs and IT managers need to consider a number of aspects when deciding to integrate cloud services into their existing infrastructure. Cost, security, performance, availability and reliability are just a few of the criteria. There is one more factor to consider: elasticity.

An elastic infrastructure makes it possible to expand or reduce processor, memory and storage resources as required. This allows the insurer to react dynamically to peak loads without having to plan for fixed IT operating costs in the long term. Requirements include metrics and a high degree of automation in addition to an elastic architecture.

The added value of an elastic infrastructure becomes apparent for insurance companies when, for example, peak loads have to be cushioned during year-end tariff setting for a motor vehicle insurance company, or when the load on portals has to be relieved after the provision of new/additional functionalities. It also helps to reduce costs as regards excess capacity, as there is no need to keep this additional equipment on hand.

Scaling enables elasticity

‘Elasticity’ and ‘scalability’ are terms that are often used interchangeably, but an elastic infrastructure is not possible without scaling of resources. However, a system can certainly be scalable without meeting the requirements for elasticity. For example, with preparation, large monolithic systems can be scaled across several machines, but reacting to peak loads, for instance, is only possible within the limits of the hardware.

The performance of a system can be achieved via horizontal or vertical scaling

The performance of a system can be achieved via horizontal or vertical scaling

Cloud elasticity requires preparation of the system landscape

Scaling one application alone is not enough. A number of issues need to be considered in order to be able to create an elastic cloud infrastructure, such as:

  • Are (all) applications already running in the cloud?
  • Has the application landscape already been migrated in its entirety?
  • Are the application launch times reasonable?
  • Are the usage metrics already well defined?
  • Do the applications scale cleanly or, in an ideal case, are the applications stateless?

What we can offer you

We identify the unique challenges you may encounter when establishing an elastic infrastructure. Based on the results, we work with you to create an architecture that adapts flexibly to your current and future requirements. adesso is a partner of leading cloud providers and can offer you technology-agnostic advice regardless of whether your preferred platform is Amazon Web Services (AWS), Microsoft Azure, Google Cloud, IBM Cloud or Oracle Cloud.

Your contact
Stefan Rogge

We look forward to hearing from you.

Save this page. Remove this page.