In addition to programming, developers are often forced to deal with fine-tuning and automation of infrastructure or to explore methods of working with specific cloud providers. Zerops offers the developers maximum comfort and full automation of operations, resulting in less time and stress involved not only for developers, while also ensuring optimum and stable operation. Let’s have a look at some examples of what Zerops can do autonomously or with the highest level of comfort for the users, i.e. the developers.
What developers don’t want to deal with (but often have to)
According to our surveys, most developers choose sizing for new applications, that is cloud performance, by trial and error, however qualified their choice may be based on data volume, previous experience, estimate, etc. Developers should not have to struggle with choosing whether to use m5.12xlarge or t2.2xlarge performance for a part of the application or a database, while also comparing hundreds of different, often incomparable items in extensive price lists.
So how is this done in Zerops? Performance options will of course be available in Zerops as well, and they will not limit the users with packages with a fixed ratio of individual performance parameters, allowing the users to select any parameter in different ratio to another parameter. Zerops will deal with the correct distribution within its architecture on its own. If, however, the user does not want to select any performance level, Zerops will select the lowest possible performance recommended for the type of application, and very rapidly scale it on the run so that it corresponds to the actual need and prevents overload or termination of processes due to, for example, insufficient memory.
Our experience at VSHosting tells us that most users consider load balancing a black box and prefer to rely on our best practices and on our optimum setup and customization of the load balancer based on the client’s application. Zerops takes a similar approach and performs automatic configuration and customization based on the given application if the user does not want to select any of the options.
Autoscaling has many configuration options. It is necessary to choose vertical or horizontal scaling, whether the application anticipates it, and to also choose the right scaling metrics that will control the autoscaling. Developers often tackle the issues whether to scale based on load, traffic, application error rate or for example based on a specific number of connections. The intelligent Zerops autoscaling selects the most suitable method of automatic scaling based on detected application behaviour.
It is certainly not the developer’s job to find out which container crashed or to assess whether and which infrastructure parameters should be adjusted to make the application run better. Zerops shows the users and reports to them the status of individual services, while also being capable of dealing with most operations issues automatically. Using slack or e-mail, it can also report to the clients recommendations for modifying the application in order to improve its behaviour (e.g. optimization of slow SQL queries, etc.).
The all-saving Docker?
Most users I talk to say that Docker is a great tool and that they could not imagine deploying and running production infrastructure without it. However, they have also noted that in the case of persistent database-type services, which are much more demanding in terms of fine-tuning, where the deploy requires users to e.g. change data structure in the database at the most, it is more suitable for developers for these services to be a kind of a reliable “black box”, with which they communicate via API and then “it just works”. This is exactly the approach of Zerops. We want to give the developers full freedom in using docker for their applications and to ensure the highest reliability of running related stateful services (please see also - Advantages of MariaDB/MySQL in Zerops – https://blog.zerops.io/mysql-mariadb-zerops-service-benefits-and-differences-over-traditional-cloud/).
No “Cloud Architect” consultants
The unnecessary corporate complexity of cloud services like AWS also often creates new positions such as the Cloud Architect. In other words, these are consultants who compensate for the lack of ergonomics of the cloud layer and create more redundant load and unsystematic features for the client. The goal of Zerops is to create a fully automated infrastructure with top-class support, but without utilizing external consultants. We want developers to manage launching their applications in Zerops even if it is their first Zerops login, within a few minutes, without having to read hundreds of pages of documentation.