Jelastic Smith 4.9 Fights Off Overload with Full Automatic Scaling and Sequential Deploy
Today we are announcing the launch of a new 4.9 release – Jelastic Smith: Replicated not Overloaded. This product version includes a set of advanced improvements connected with horizontal scalability and sequential deploy of multiple containers.
“Ability to scale applications quickly and easily according to the business growth is one of the most highest customers expectations. Starting from Jelastic Smith version, various scaling triggers can be defined for any container or layer in multi tiered applications, that makes existing horizontal scaling even more advanced and automated,” said Ruslan Synytsky, Jelastic CEO and co-founder.
Automatic vertical and horizontal scaling of containers is one of the key features provided by Jelastic to their customers. In the latest release this functionality was extended to all kinds of certified (databases, load balancers, application servers etc.) and custom Docker containers.
Within Jelastic dashboard a customer can define the environment topology and distribute the containers to the needed layers. After that automatic horizontal scaling can be set up for every type of container due to the specific triggers.
“At Scaleforce we are very excited to welcome the most advanced horizontal scaling for Docker containers provided by Jelastic. The automated horizontal scaling is now available for database servers, storage containers and custom Docker containers but not only for web application servers. This provides an extra layer of peace for our clients. In addition, a new sequential restart on multiple containers with the configurable delay from 30 seconds up to 5 minutes, allows complex applications to remain fully operational during the deployment or resource allocation. Every release Jelastic delivers important new features, and 4.9 version made the platform even better fit for enterprise implementations such as WebLogic Server Applications. We are already looking forward to the next release!” said Theodoros Filippidis, CEO at Scaleforce, United Kingdom.
In confines of Jelastic 4.9 release, the horizontal scaling feature was also implemented for the Dedicated Storage Container node type. So from now, users can handle various development scenarios that require several separate storage nodes, allowing to run some specific applications and achieve data redundancy.
“The newest Jelastic version has brought a very popular feature, automatic horizontal scaling, to all Jelastic containers. Our customers were requesting horizontal scaling especially for Docker containers. It is great that we can respond the customers needs and they can host more complex environments really cost-effectively in Jelastic Cloud.” said Heidi Eronen, Product manager at Planeetta Internet, Finland.
When scaling servers out within Jelastic environment, users automatically gain the advanced availability for their application or service. This is ensured with the sequential restart & deploy functionality. Such approach allows to perform various operations like container restart, application deployment, Docker container update and changing cloudlets number without the whole service downtime. In the 4.9 Jelastic version, this mechanism was supplemented with a special delay option. It allows to set up a particular time frame (30 seconds, by default) between running operations at containers of one layer, providing them with additional time to restore the full operability.
“We are very much pleased with the latest 4.9 version of Jelastic. The various features of automatic horizontal scaling of dockers, as well as horizontal scaling for storage containers is really beneficial for our business growth at Everdata Data Center. We would also like to mention about the configurable delay for sequential deploy which is an awesomely added feature,” said Naveen Sharma, Director at EVERDATA Datacenters, India.
More details about automatic horizontal scaling of containers, sequential restart and deploy as well as other improvements of Jelastic 4.9 can be found in Release Notes.