Three weeks ago today, Torsten, our CTO, introduced the open beta of our Load Balancer as a Service (LBaaS) with free SSL. With this load balancer, we have reacted to those multiple requests from our users. The LBaaS from gridscale can be configured with our customary comfort. In contrast to the load balancers known to us from other providers, our version can also be used when the infrastructure behind the load balancer resides with another provider. In this way, our load balancer can be deployed in many useful constructs.
The load balancer can, for example, redirect to a maintenance page when the web service is unreachable. No problem thanks to Health Check.
It is now time, after those initial three weeks, to sketch a brief summary:
- So far, 345 load balancers have been created at gridscale. Stated differently: Over 16 load balancers are being created per day.
- Barely 9% of all load balancers are operated on Layer 4, whereas 91% of all load balancers work on Layer 7.
- Slightly below half of all load balancers use our free SSL Certificate, which is a good sign. This shows that it is equally important to our users, as it is to us, in offering SSL-secured web services.
- No service requests have been created on the topic of the load balancer – meaning we have attained our goal of intuitive user guidance.
The current statistics leave me well satisfied. They demonstrate that with gridscale we provide functions and features which are extremely popular. Of course, we will not be resting now on our laurels in this area.
In the meantime? We are currently working on the next feature for gridscale and will publish this in two months, directly after conclusion of the open beta for our LBaaS.
Our strategy of continuous further development is obviously set to remain. We have caringly christened the “X-month ass-kicking-flow” for you. We thus guarantee regular updates of functions and features that save our users work and also maximize the user experience at gridscale.