Every VPS tutorial starts by asking you to choose between LAMP and LEMP, and most do not say what the choice costs. The honest answer is that for a small site it barely matters, and for a busy one it matters quite a lot.
What the letters mean
LAMP: Linux, Apache, MySQL (or MariaDB), PHP. LEMP: the same with nginx (pronounced engine-x, hence the E) in place of Apache. The operating system, the database and the language are identical. The only question is which program answers port 80.
How they differ in practice
Apache runs PHP inside the web server process by default, which is simple and is why so much of the internet was built on it. It reads .htaccess files from every directory, so redirects, rewrites and access rules can live beside the site and be changed without touching the server config. Panels like cPanel and Plesk lean on that.
nginx does not run PHP itself. It hands PHP requests to PHP-FPM, a separate pool of worker processes, and serves everything else, images, scripts, styles, straight off the disk with very little memory per connection. There is no .htaccess; rules go in the server config and need a reload. That is less convenient and considerably faster under load, because a thousand idle connections cost nginx almost nothing and cost Apache a thread each.
Which to pick
WordPress, new build, no panel. LEMP. nginx with PHP-FPM and a FastCGI cache is the fastest common WordPress stack, and the rewrite rules WordPress needs are a dozen lines you copy once.
WordPress with cPanel or Plesk. Whatever the panel installs. cPanel is Apache; Plesk runs nginx in front of Apache so you get both. Do not fight the panel.
Laravel, Symfony, any modern PHP framework. LEMP. The frameworks assume PHP-FPM and ship an nginx config in their docs.
A Node, Python or Go app. Neither in the old sense; put nginx in front as a reverse proxy for TLS and static files, and let the app serve itself behind it.
A site that depends on complicated .htaccess rules you did not write. LAMP, until you have time to translate the rules.
Several unrelated sites on one box. Either works; nginx server blocks are tidier, Apache virtual hosts have more examples online.
Installing each on Ubuntu
LEMP:
sudo apt install -y nginx mariadb-server php-fpm php-mysql php-xml php-mbstring php-curl php-gd php-zip
sudo mysql_secure_installationLAMP:
sudo apt install -y apache2 mariadb-server php libapache2-mod-php php-mysql php-xml php-mbstring php-curl php-gd php-zip
sudo a2enmod rewrite && sudo systemctl restart apache2
sudo mysql_secure_installationBoth take under five minutes on a 4 GB VPS. Add a Redis object cache for WordPress on either stack; it does more for a busy site than the choice of web server.
Sizing
A 4 GB Cloud VPS runs either stack with a WordPress site and room to spare. The gap opens when traffic arrives: nginx keeps serving at concurrency levels where Apache's default configuration starts swapping. If you expect spikes, LEMP buys you time before the next plan size.
Questions we get asked
Is nginx harder? The config syntax is different, not harder. The main adjustment is that rules live in one file and need a reload.
Can I switch later? Yes. The database and PHP code do not change; you install the other server, port the rules, and swap which one listens on port 80.
Does the choice affect SEO? No. Speed does, and both can be fast. Caching matters more than the server.
Which does URLStart install? Whichever you ask for at order time: bare Ubuntu, LEMP, LAMP, or a panel.
