One of the hard parts about learning how to develop software is the minefield of acronyms that exists in the industry. The goal of this series of articles is to shine a light on an acronym so the next time another developer uses it in conversation you can follow along without missing a beat.
In this article, we’re going to be discussing the acronym LAMP. We’re picking this acronym because we’ve used it a couple of times in other articles and in doing so we have to use other acronyms which we’ll define in future articles. :-)
What Is LAMP?
LAMP is a shorthand way to communicate the major technologies used in our web service stack. Every web service needs at least four components:
- An operating system
- An HTTP server
- A persistence layer
- A programming language
The acronym LAMP comes from the first letters of each of the technologies that are used.
- Linux Operating System
- Apache HTTP Server
- MySQL Database
- PHP/Python/Perl Programming Languages
The lovely thing is that all of these layers can be swapped out if we have different needs. When we do that it creates a new acronym for us to use.
For example, if we’re swap out Window for Linux we get WAMP.
Using macOS? Now we’re talking about MAMP.
What if we’re using PostgresSQL? It’s now LAPP.
Prefer Enginx? We’re running a LEMP stack.
As you can see there are a huge number of possible combinations all with their acronym.
As always, if you have questions related to LAMP or the PHP ecosystem you would like us to answer in future articles please ask them in the comments below and we’ll add them to our list.
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows