My question is that is the P part of the LAMP really necessary? I will have the database and I can connect to it via the appache http so why will I need php/python in the server side (if it is a really simple set up)

also from a seperation of concern it might be more robust at least thertically to leave the P out of the equation and to use LAM only.

What are you guys think? I need to build this as a linux server in order to backend mobile ios and android.


closed as unclear what you're asking by gnat, GlenH7, GrandmasterB, user40980, Wayne Molina Aug 29 '14 at 0:50

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.


The “P” part of a LAMP stack is a layer of CGI scripts. This layer can be provided by a number of languages. While PHP is the most common of these, other languages such as Perl or Python can be used as well.

While a LAMP architecture is common and robust, it may not actually match your needs. For example it might make sense to not use CGI scripts and leave out the “A” (Apache HTTP Server), and use a more integrated web framework of your language of choice instead. When using Perl, a common stack would be to utilize Linux running a Perl application built around the Mojolicious web framework, using Starman as a server and PostgreSQL as a DB, and running behind Nginx as a caching proxy. Which stack to choose depends directly on the project you are tackling, and on the technologies you (and your team) are familiar with.


LAMP is just a convenient platform. If part of it doesn't fit your needs -- like, for example, you need run a windows server for $REASONS -- then replace that part.

Not the answer you're looking for? Browse other questions tagged or ask your own question.