Who can save 12306?

on January 9, there have been a lot of white-collar workers begins to release in succession The day before the holiday ticket, and the already sluggish 12306 into a complete "eternal", the error of the Blue window screen with a variety of spit-filled micro bo. According to the Sina survey, about 87.9% of netizens said 12306 paralysis has affected the normal purchase of tickets.

In many complaints, one of the most common type of complaint is "people pay treasure 24 hours trading 35 billion are not paralyzed, I think as long as Ma took over, then 12306 will not be so!" ”

In fact, this subtext is self-evident: the state-owned enterprises spend a few billion 12306, the effect is far less than Baidu, Taobao, Tencent and other internet giants, if Tiero willing to put down their posture and "Ma" cooperation, then 123,061 will not reap so much of the curse.

The wish is very good, but I am afraid it is not so simple.

First of all, as an Internet product, the user's expectation for 12306 is "to provide a fast and stable ticketing service". Users of the "site paralysis" complaint is only the appearance, do not think that the general public really care about whether the 12306 is really stable, people really can't stand is "this site why not sell me train tickets." On this basis, will be traced, all the way to 12306 of the server enough, "Ma" and state-owned enterprises which level of high and their own needs of the original irrelevant topic.

Second, give 12306 to "Ma Yun", can do less collapse, and even provide the same as the Internet giant stable service it? No problem.

"Ma Yun" in fact already in the rescue 12306--with the help of the third party team, the Iron Academy has gradually 12306 of the rest of the ticket query system and booking query system from the hard drive moved out, put in the server's memory resource pool. In addition, Ali and other Internet companies are also involved in the transformation of the 12306 queuing system.

Of course, this improvement is still far from enough, 12306 still have a bloated front-end and UI (cause part of the crash), not enough human to buy the ticket process (with all kinds of ticket assistant experience is very far away), and these long-standing issues have not been criticized by the Iron Institute seriously resolved. If you give these questions to the "Ma", do not think they will still be the reason for the system short board.

From a purely technical point of view, for a full year of pressure in a few weeks of the ticketing system, betting on the resources of several internet giants, regardless of cost, the national 2369 pairs of passenger trains are separately equipped with separate processing cluster, certainly will not appear the problem such as the collapse of cotton.

But back to the original question. Can such a solution really save 12306?

"Ma Yun" approach to achieve the ultimate, is lets the user originally need to spend several hours to brush the website the experience, becomes "the second kill"--is true, assumes the system ability to become infinite big, is enough real-time response Spring Festival travel time maximum daily 10 million users each mouse clicks, does not collapse the consequence is the ticket instantaneous rob empty.

During the Spring Festival, the overall shortage of railway capacity, destined to lead to 12306 of the performance regardless of how to optimize the user to buy tickets will not increase the probability, the demand is not met. Many people see, will be a time to put the ticket, quickly tell you "no ticket" site.

So, "Ma Yun" can guarantee 12306 not crash, but "Ma" does not guarantee that users to sit on the train home.