The use of scripting languages started with the Common Gateway Interface Web interfaces of the early 1990s, simplifying the delivery of Web pages with dynamic, updated content in addition to static, unchanging pages.
Programmers preferred scripting languages for these applications because they made it relatively easy to manipulate text streams from a variety of sources.
The acronym LAMP was coined by writer Michael Kunze in an article in the December 1998 issue of German computing magazine Computertechnik. Kunze was trying to show that a bundle of free software could be a feasible alternative to expensive commercial packages. Since then, publisher O’Reilly & Associates and MySQL have worked to popularize the term.
Platform or App Stack?
Many refer to LAMP as a stack, a layered grouping of basic business software. These layers are comparable with the ones that make up commercial stacks like Microsoft’s .Net framework. When used in combination, they support application servers.
Competing stacks of commercial middleware include unified application development environments such as .Net, IBM’s WebSphere, Apple Computer Inc.’s WebObjects and Sun Microsystems Inc.’s Java Enterprise Edition. But whether we call LAMP a stack or a platform, it clearly qualifies as having an interlocking set of technologies on which developers can build and deploy applications.
Is LAMP ready for use inside the enterprise? Yes and no. It’s already used to run high-volume Web sites, such as the O’Reilly Network. Major chunks of Internet giants such as Amazon.com Inc. and Google Inc. use LAMP systems and networks. But you probably wouldn’t want to run your core financial systems on LAMP; until recently, MySQL didn’t even understand the notion of a transaction.
By itself, LAMP really only defines software for Web applications. Although you can use it to build an application that connects to sophisticated middleware, the heavy-duty programming would likely have to be done in a different language.
The .Net and Java platforms, in contrast, offer a way of writing both Web scripts and complex enterprise applications in the same language.
Still, LAMP is likely to be popular with price-conscious organizations that have strong internal development efforts and are comfortable with peer-based support. Does that fit your company’s environment and culture?
Kay is a Computerworld contributing writer in Worcester, Mass. You can contact him at firstname.lastname@example.org. Are there technologies or issues you’d like to learn about in QuickStudy? Send your ideas to email@example.com.
See additional Computerworld QuickStudies
Read more about App Development in Computerworld's App Development Topic Center.
- The Business Value of Continuous Delivery Download this whitepaper to learn more about the business value of Continuous Delivery and see why it could be a game changer for...
- Ten Factors Shaping the Future of Application Delivery Download this research report conducted by Enterprise Management Associates (EMA) to learn how those that are seeking to accelerate application delivery are leveraging...
- Adobe Creative Cloud FAQ The following are answers to common questions about Adobe® Creative Cloud™ for teams membership, purchasing, security, and storage.
- What's coming to Adobe Creative Cloud Editing and video content creation workflows are about to get easier and more exciting, with major updates coming soon to Creative Cloud, bringing...
- NSS Labs & Cisco Present: Evaluating Leading Breach Detection Systems Today's constantly evolving advanced malware and APTs can evade point-in-time defenses to penetrate networks. Security professionals must evolve their strategy in lockstep to...
- Will the Real Endpoint Threat Detection and Response Please Stand Up? This webinar explores new technologies & process for protecting endpoints from advanced attackers as well as the innovations that are pushing the envelope... All App Development White Papers | Webcasts