Nginx market share soon to hit 10% mark

By -
According to multiple sources such as:

the amazing and lightning-fast web server known as nginx is just about to hit the 10% market share mark in the next couple of months. This is a fantastic milestone for the author, Igor Sysoev, who probably didn't imagine that the application (which he originally developed on his own) would meet such fame.
Diagram courtesy of W3Techs.com (article linked above). Its market share went from a little over 5% to almost 10% over the last year as you can see. 

I wouldn't go so far as to say that the release of my Nginx HTTP Server book (released Summer 2010) was one of the factors that contributed to the popularity of the Russian web server. It is my belief that the sole quality and efficiency of the software is what made its success.


The book was and is being translated into three languages:
  • In Japanese
  • In Chinese (to be published soon)
  • In Korean (release date unknown) 
Nginx is already a popular web server in Russia and Asia; some of the most popular websites in these regions are powered by nginx; namely Yandex, 163 (China's #1 e-mail platform), Soso.com, Renren.com, and more internationally Wordpress, among many others. My own websites GBAtemp.net, FileTrip.net, ShopTemp.net are powered by nginx as well.

Comments

Anonymous said…
Your book is great. Thank you!
Wed Jan 18, 12:54:00 AM
facebook iniciar sesion celular said…
I would like to thank you for the efforts you have made in writing this article.
----
facebook móvil and facebook movil gratis and apply facebook iniciar sesion
Thu Aug 06, 04:09:00 PM
Post a Comment

Popular posts from this blog

Affiliate module for Interspire Shopping Cart

By -
Image
Hello, I have already implemented this module on two shops rather successfully. The concept is quite simple: websites that want to get rewarded through affiliation must link to your website using an identifier in the URL. If your website is http://website.com/, then your links must be of the form http://website.com/?ref=123 where 123 is the affiliate ID. when a visitor clicks the link, the affiliate ID will be placed in a cookie that will expire after 15 days (this can be configured) when the visitor purchases an item: if the affiliate ID cookie is still enabled, the affiliate will be credited of a certain amount, it can be a share of the sale or a fixed amount. affiliate accounts are simple customer accounts, there is no modification to make regarding accounts. When a sale is made, they receive store credit. They can either spend the store credit to purchase items on the store, or they can manually request for a withdrawal (managing withdrawals is up to you). I will detail the i
Read more

Nginx error 413: Request entity too large Quick Fix

By -
A quick article today about a common error people encounter with Nginx: the infamous 413 Request Entity Too Large HTTP error. I had the problem myself just yesterday on one of my newly configured servers, so I thought I'd make a blog post about it to make sure I don't forget this next time. Error 413: what does it mean? This error shows up when a visitor sends too much data in the HTTP request. This is normally caused by: • an overy large file being uploaded by the visitor • more generally too much POST data being sent by the client The fix is as simple as setting a directive in your Nginx configuration, read on below. How to fix it? client_max_body_size To fix this, you need to increase the value of the client_max_body_size directive. This directive defines the maximum amount of data Nginx will accept in an HTTP request. By default this value is set to 1 megabyte, meaning if you attempt to upload a file larger than 1 megabyte you'll be getting an  Error
Read more

Dealing with Nginx 400 Bad Request HTTP errors

By -
Today I'll write about something I experienced personally, on my websites. Some visitors reported that they were getting a "400 Bad Request" Nginx error randomly when visiting pages. And when they start getting that error, they can't access the site anymore: it'll output the same error no matter the page, until you "clear your cache and cookies". The error is easily understandable and is likely to be caused by... too much cookie data. Every time a visitor loads *any* page/content/file of your website, it sends the cookie data to the server. Cookie data is sent under the form of 1 header line starting with "Cookie: ". Basically, Nginx by default is configured to accept header lines of a maximum size of 4 kilobytes. When a line in the headers exceeds 4 kilobytes, Nginx returns the '400 Bad Request' error. Cookie data sometimes gets big, so it causes the error. It particularly happens on forums like vBulletin, Invision and others
Read more