Editing Portal:SaaS and Web Development (section)

=== mod_perl ===

The next major step in Perl web development was '''mod_perl'''. mod_perl embedded a Perl interpreter directly into the Apache HTTP server, allowing Perl code to run inside Apache rather than starting a new Perl process for each request. The official mod_perl site describes it as bringing together the full power of Perl and the Apache HTTP server, allowing Perl to manage Apache, respond to web requests, and more.<ref>Apache mod_perl, “Welcome to the mod_perl world,” https://perl.apache.org/, accessed July 3, 2026.</ref>

The first version of mod_perl was written by Gisle Aas and released on March 25, 1996. Doug MacEachern and Andreas König then helped continue the project’s development.<ref>Apache mod_perl, “History,” https://perl.apache.org/about/history.html, accessed July 3, 2026.</ref>

mod_perl solved a major CGI performance problem. Because Perl and application code could remain loaded in memory, requests could be served much faster than traditional CGI. Database connections, compiled regular expressions, configuration data, and Perl modules could be reused across requests.

mod_perl also gave Perl programmers access to the Apache API. This meant Perl could be used not only to generate pages, but also to write Apache handlers, authentication systems, filters, logging tools, configuration logic, and custom server behavior.

In practice, mod_perl had two identities. First, it was a way to accelerate existing CGI-style applications. Second, it was a deep Apache programming environment. The first use was easier to understand and more common. The second was more powerful and more specialized.

mod_perl helped power some of the most important Perl-era web applications and sites. It also influenced how Perl programmers thought about persistent web applications, long-running processes, memory management, and application architecture.