nginx vs litespeed vs apache

DenisMNE

Corporate Member
Corporate Member
Joined
Apr 11, 2018
Messages
108
Best answers
0
Ratings
9 2
Points
18
#1
Which one do you use and prefer ?

Interested in pros and cons of both and which is faster.

I've heard recommendations for litespeed but wanted to check it out here firstly.

Thanks.
 

Blizbox

Well-known member
Joined
Mar 25, 2018
Messages
94
Best answers
2
Ratings
36 5
Points
18
#2
We use litespeed. It comes at a price but worth it. It's architecture is different to Apache in the way it uses resources. It's a lot more efficient which makes for better performance.
 

AlbaHost

Well-known member
Joined
Jan 18, 2017
Messages
289
Best answers
1
Ratings
70 4
Points
28
#3
If you want free alternative you won't go wrong with nginx.
 

hostens

Well-known member
Joined
Jan 18, 2017
Messages
160
Best answers
2
Ratings
54 6
Points
28
#6
Best answer
It depends on what you wish to achieve as they have their strengths and weaknesses.

Apache is great for running small sites. However, it is not great for many concurrent connections, requires a lot of RAM. Can stop working when the load is high because it is process based.

Nginx is great for handling a lot of simultaneous connections on the same server and consumes a little less memory than Apache because it is event based. However, it is not that good for customization and also does not read ".htaccess".

LiteSpeed also uses the event-driven approach as Nginx. The benefit of it is that it also has some strengths as Apache - you can use ".htaccess", "mod_security", "mod_rewrite" and many more. You can easily transit from Apache to LiteSpeed. However, it is commercial.

If you are willing to buy a license, it is always great to have official support available and I would recommend choosing LiteSpeed. It has strengths from both Apache and Nginx. In another case, I would go with Nginx.
 

DenisMNE

Corporate Member
Corporate Member
Joined
Apr 11, 2018
Messages
108
Best answers
0
Ratings
9 2
Points
18
#7
DenisMNE
Well, that was detailed.Thank you.
Thank you for giving me a more deep look into it.
As said, my budget is tight so I have no options.
LiteSpeed should be my choice when the money allows.
As you said, nginx is good for handling a lot of simultaneous connections, that will do for the beginning.
 

djsmiley2k

Well-known member
Joined
Jul 10, 2016
Messages
116
Best answers
0
Ratings
4
Points
18
#8
djsmiley2k
Nginx is great for handling a lot of simultaneous connections on the same server and consumes a little less memory than Apache because it is event based. However, it is not that good for customization and also does not read ".htaccess".
The best way to use Nginx is using Plesk control panel, that will help us not need too many configurations manually?
 

VirtuBox

Global Mod
Staff Member
Joined
May 3, 2016
Messages
1,500
Best answers
4
Ratings
380 10
Points
83
#9
It depends on what you wish to achieve as they have their strengths and weaknesses.
Apache is great for running small sites. However, it is not great for many concurrent connections, requires a lot of RAM. Can stop working when the load is high because it is process based.
Nginx is great for handling a lot of simultaneous connections on the same server and consumes a little less memory than Apache because it is event based. However, it is not that good for customization and also does not read ".htaccess".
LiteSpeed also uses the event-driven approach as Nginx. The benefit of it is that it also has some strengths as Apache - you can use ".htaccess", "mod_security", "mod_rewrite" and many more. You can easily transit from Apache to LiteSpeed. However, it is commercial.
If you are willing to buy a license, it is always great to have official support available and I would recommend choosing LiteSpeed. It has strengths from both Apache and Nginx. In another case, I would go with Nginx.
One of the reasons of Nginx better performance compared to Apache is the fact it doesn't use .htaccess. For every connection, Apache check if there is a .htaccess, then read the .htaccess and finally display the page to the visitor. It's not an efficient process to handle traffic.

With Nginx, you just have to set the rewrite configuration one time, and it will just do the job with low footprint on your resources.

. However, it is not that good for customization and also does not read ".htaccess".
What do you mean by customization ?
 
Newer Threads
Latest Threads
Replies
0
Views
6
Replies
5
Views
25
Replies
0
Views
1
Replies
2
Views
27
Recommended Threads
Replies
0
Views
1,135
Replies
15
Views
1,583
Similar Threads

Latest postsNew threads

Latest Hosting OffersNew Reviews

Sponsors

Latest Blog ArticlesMost Viewed Threads

Top