Introduction to LiteSpeed
- 1. Gabriel Răileanu December 11, 2019
- 2. Agenda 1. Web Server? Why we need it? 2. LiteSpeed 3. LiteSpeed WebServer VS others 4. LiteSpeed Cache 5. Q/A? 2
- 3. Web Server? Why we need it? 3
- 4. - web serving - load balancing - cache acceleration 4
- 5. LiteSpeed WebServer - C/C++ - event-driven architecture - Apache drop-in - Anti-DDoS protection - HTTP 1.1/2.0/3.0 - runs on Linux/Solaris/FreeBSD/MacOSx - used by many web hosting company, especially in last period 5
- 6. LiteSpeed WebServer - the purpose of introducing this web server was to read Apache configuration file - lightweight software, based on resource conservation - better than the general-adopted solution (Apache) - but… paid 6
- 7. OpenLiteSpeed - open-source GPLv3 version of LiteSpeed WebServer - developed by LiteSpeed Technologies, with support from the community - the code is binary (needs to be compiled & executed by sysadmin/DevOps/developers): optimized for your computer/datacenter - has no 1-click install, but are some scripts for easy run developed by community 7
- 8. OpenLiteSpeed vs Apache ● Apache: still the most popular, but the oldest (free) web server ● LiteSpeed is an drop-in alternative for Apache (config files, rules, mod_security, mod_rewrite) ● OpenLiteSpeed offers support for .htaccess files ● OpenLiteSpeed is asynchronous (because it’s event-driven). Apache is process based. ● OpenLiteSpeed is better when a DDOS is initialized, better in big traffic situations 8
- 9. OpenLiteSpeed vs Nginx ● both open-source, based on event-driven architecture ● unlinke OLS, Nginx is not Apache drop-in replacement ● Nginx does more than serving HTTP requests (load balancing, reverse proxy, API gateway, firewall) ● OLS stores cached files, Nginx not 9
- 10. 10
- 11. 11
- 12. LiteSpeed Cache ● open source; server-side page cache ● plugins for different platforms ● (dynamic) php content is compiled only once, then the screenshot is served ● uses (Edge Side Includes) 12
- 13. 13
- 14. Q/A? 14
- 15. 15