Airi — cloud website


We have recently launched a new service — cloud for the site, Airi.Russian. Cloud for the site — this is when the whole site is light, transparent, airy and fast. No images, scripts, complex server-side logic, databases, and no DDoS can't get it down. This is when the website is flying. We realize their dream — now any site regardless of platform, internal characteristics or logic of the client can be put in the cloud. And he will work faster and more reliable on all devices and for all users. And it's available for both the smaller sites and for the largest.

Yes, it is similar to Western CloudFlare. And the original model is the same. But only on the expanses of Russia, according to its geography. And evolve we plan differently.

P. S. at the moment Irie is in beta stage, we actively recruit the first users, although the service has already moved into commercial operation, and reliability is a priority.


the

Architecture


Originally we planned to make several components of the service, the maximum splitting levels of responsibility. But later, due to various kinds of restrictions on data integrity and fault tolerance of the system, we came to the following architecture:

The whole service is divided into geographically independent sites, users are directed to a particular node depending on the IP addresses and DNS records. DNS records of geo-balanced (in case of failure of any node we for a short period of time can redirect local users to another node).
    the
  1. Layer DNS. Each node is a pair of servers configured with LVS for maximum fault tolerance. Further zone on different DNS servers respond differently to different regions, creating a geo-balancing.
    2. the
  2. Layer load balancer (LVS). The basic machines that take the entire load. They are intended to connect to the DDoS protection and the distribution of queries at various FEO-CDN servers depending on the domain of the website.
    3. the
  3. FEO-CDN layer (Front-End Optimization and Content Delivery Network). Each node is a caching and optimizing cluster of proxy servers. The architecture of this layer we thought long and continue to think about how to optimize and the operation of the site, and the load on the server. At the moment we have 4 levels of caching and proxying:
      the
    1. Front-end level, it only compresses (using gzip) the content and caches the final HTML page sites if needed. If query is not in the cache, then proxy them on. Collects statistics on the given content.
      2. the
    2. Optimization level. There is a Page Speed with some of our improvements in the part of the lazy loading and caching dynamic pages. The most difficult level from the point of view of the algorithms. All requests not from the cache are sent to the level below.
      3. the
    3. the Caching level. Caches the entire statics and dynamics. Gives everything from the cache if it can. If not — asks the original site. Also classifies low-level queries, and provides the decompress (unzip) the data from the source site.


the

Balancing and failover


During the implementation we considered several scenarios of denial of service (or website). Bring some of the highlights:
    the
  1. Failing DNS layer of any node connects the second of the LVS-pair. If you deny both servers, then DNS queries (with exactly the same content) begins to respond to DNS layers of other nodes.
    2. the
  2. Denied both servers LVS-a pair of balancing layer of any node. In this case, due to a DNS balancing, requests are automatically routed to other nodes.
    3. the
  3. Deny (overloaded) FEO-CDN layer — automatically connect extra spare servers in this layer. If no servers are, then act according to the previous scenario, we set the sites to another host.
    4. the
  4. Original site goes down (becomes unavailable). If the site is cached and the period of unavailability is less than the lifetime of the cache, users will notice nothing. If the period of unavailability for less than a day, continue to issue page from the cache. For dynamic sites — individual policy (parked page, the cached content or redirect).

The main problem areas and risks are eliminated by the architecture, so we can talk about fault tolerance is 99.9%.

How does acceleration


The most difficult and interesting — how does the acceleration. We analyzed the available filters, Page Speed, and gathered from them a few options suitable for most sites. And called levels of acceleration accordingly: Secure (when any harm to the website is guaranteed not to be caused by), Minimum (when there is minimal risk of harm to the website), Optimal (suitable for most sites, provides significant acceleration, but potentially dangerous) and the Maximum (most risky and the most effective option). In addition, we offers and manual setting of all parameters, if necessary (in full compliance with the existing policy of customization of our product — WEBO Site SpeedUp).

Let me emphasize that by default, all static objects of the website are cached for a long time, and all the text is securely archived. In addition, is available to merge the files, the inclusion of small objects in the content of the pages, the logic of lazy loading and Local Storage, and the use of multiple domains and data:URI for images. In General, the complete beef for those who want to customize everything. And a guaranteed level of speed and reliability of the site for everyone else.

In conjunction with geo-balancing of requests (website visitors get the site objects from the closest server to it) we solve all problems with site speed "one-click".

the

Rates


We came as friendly to the users and proposed rates free (included 50 GB in a month) to the maximum (50 thousand rubles). The average website can connect 1000-2000 rubles per month (this includes 100-250 GB of traffic per month, enough to 100 thousand users per month).

the

Connect


There are two basic kinds of connection: by changing DNS servers and CNAME using a synonym www. In the first case, we connect the domains that only available without the www (e.g., Irie.RF) — to delegate the domain to our servers so we can fully manage your geo-balancing.

The second type of connection is suitable for sites that are only available via www or both. In the latter case, it is necessary to make the redirect site without www to the site with www and create a DNS entry for the site
the 
www IN CNAME cloud.airee.ru.

The site will be served via the cloud.

Of course, all these steps must be completed before after submitting. We don't serve all domains of the Russian Internet :)

In the near future will appear and a personal account for cloud management.

I will be glad to questions and comments. Our goal is to make Irie de-facto standard when placing sites.
Article based on information from habrahabr.ru

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Vkontakte sync with address book for iPhone. How it was done

Изображение
the Background application on androidphone when you install the application Vkontakte is possible to use it as a provider of contacts to synchronize the contacts from Facebook with contacts in your address book. In this case stretches the avatar, date of birth, address, phone numbers, etc. When I after prolonged use HTC Wildfire S rated and are so used to this that he wanted to find a similar to the iPhone. Not found, so we took it and made his own — Synchronizer VKontakte :) It was back in November of last year. The application was done fairly quickly — it uses quite a few functions of Vkontakte API and functionality with the address book of the iPhone. But when we started to deal with the automatic matching of contacts, it was fun. Compare head-on by name, last name and phone number was easy to do, easy, and worked through it quickly. But found only 20 percent of coincidences of the contacts from what is provider in Android. Of course, only direct hits do not sui
Далее...

Automatically create Liquibase migrations for PostgreSQL

Изображение
Working with Liquibase always brings confidence in the fact that the database objects are in the same condition in which you want it. It is this confidence and makes system migrations so popular databases. Today I want to tell you how to make using liquibase a bit easier. If you write a migration by hand, and your target database is PostgreSQL, then read this article, I am sure, the time spent on reading the article will be repaid with interest. I hope you already know how to work with Liquibase, so only two words describe how the system works. In order to make changes in the database, you need to create a migration file (changeset) that you need to specify in the file change log (changelog), after which the migration can be successfully applied to the target database. Undeniable and obvious benefit of this approach is the ability to rollback the changes. In my opinion, liquibase, there is only one drawback — the automatic rollback of changes only works only if the mi
Далее...

What part of the archived web

Изображение
/ > the time Machine Internet Archive is the largest and well-known archive that preserves web pages since 1995. Besides him there are a dozen other services, which are also archived to the web: the indexes of search engines and industry-specific archives like Archive-It , UK Web Archive , Cite Web , ArchiefWeb , Diigo . Interesting to know how many web pages gets into these files, relative to the total number of documents in the Internet? It is known that the base of the Internet Archive for 2011 contains more than 2.7 billion URIs , many of them in multiple copies taken at different points in time. For example, the home page of Habra "photographed" already 518 times since July 3, 2006 . It is also known that the base reference Google five years ago overstepped the mark in trillion unique URLS , although many of the documents were duplicated. Google is not able to perform all URLS, so the company decided to count the number of documents in the Internet a
Далее...