Some time ago, we announced that we were looking for a driven entrepreneur who can help accelerate our business. That entrepreneur has been found and we are happy to welcome Mikael Dahlgren aboard as our new CEO. He has been working with us since the beginning of September, and has already met a few potential customers of ours together with our CTO, Johan Tordsson. As he is gearing up for driving this company into a better and brighter future, we would also let our blog readers learn a bit about him.
In our previous post, we briefly introduced the basics of auto-scaling. What auto-scaling is, why it is important, and how it works, including monitoring, metrics, and all that jazz. In this post, we will dive deeper. We will see how an auto-scaler determines by how much it needs to scale your deployment and what one looks like internally. We use the Elastisys cloud platform for illustrative purposes — we develop it, so it is obviously the one we know best. We also discuss how it uses predictions to pro-actively determine future capacity demand and gives you just-in-time capacity. Grab a nice cup of coffee (might we suggest a nice caffè mocha?), and read on!
What different types of scalability are there, and how do you design for them? Elastisys is a spin-off from the distributed systems research group at Umeå University. As such, we have extensive knowledge and experience in designing and developing scalable distributed applications. In this post, we list some of our best tips to help software architects and CTOs design with scalability in mind.