Linux network stack performance has become increasingly relevant over the past few years. This is perfectly understandable: the amount of data that can be transferred over a network and the corresponding workload has been growing not by the day, but by the hour.
Not even the widespread use of 10 GE network cards has resolved this issue; this is because a lot of bottlenecks that prevent packets from being quickly processed are found in the Linux kernel itself.
On September 1, 2015, a law came into effect regarding how the personal data of Russian citizens is stored. Although over a year has passed, the law is again making headlines as the social network LinkedIn was recently blocked for failing to comply with new legal requirements. Today, we’d like to clear up some of the confusion surrounding this legislation and what exactly is stipulated by it.
We recently wrote about our switch to a new platform, which has let us make big improvements to our Cloud Storage. We talked about how we developed our storage’s logic and architecture, as well as how we rewrote several components in Go, which makes our storage even faster and more stable than before.
Big News: We’ve rewritten our Cloud Storage API! The system is much more stable and quicker thanks to the new platform, Hummingbird. Hummingbird is essentially an implementation of several OpenStack Swift components written in Go. We’ll discuss how we implemented hummingbird and what problems it helped us solve in this article.
The Virtual Private Cloud lets you create virtual machines from a wide-range of existing OS images.
However, some users need images which our service doesn’t offer. These include less common kinds and versions of operating systems.
Selectel offers a wide variety of services, and a number of different people work on each one: software has to be developed, code written, and the infrastructure managed. To simplify and speed up the development and implementation process, we decided to create our own “CI lab”. For continuous integration, we use Jenkins.
In addition to writing code, a lot needs to be done before a program can be launched. This can be very time consuming. It might not seem like much—combine everything written by different developers, create an installer, prepare the documentation—but most programmers can’t imagine just how much time these fairly routine operations actually take. It’s not that uncommon for an entire team to rush to get their work done, but that only creates more errors and issues. These problems take time to resolve, and inevitably, the product’s release gets pushed back to TBA.
Nobody likes it when their servers go offline, even if it’s just for a moment. Unavailability, which is often caused by a single malfunction, could result in serious financial losses. To bring everything back to working order, the cause first has to be identified, and then the necessary repairs have to be made.
Last year was a banner year for Selectel. Of all our accomplishments, one in particular affected not just our clients, but the entire Internet communit: being chosen to host a K-root DNS node. In this article, we’ll be talking about what this all means and how we came by this prestigious responsibility.
