This "one new process per request" model makes CGI programs very simple to implement, but limits efficiency and scalability.
To address the scalability shortcomings of CGI, Open Market developed FastCGI and first introduced it in their webserver product in the mid-1990s.
The connection may be closed at the end of a response, but both web server and FastCGI service processes persist.
This separation allows server and application processes to be restarted independently – an important consideration for busy web sites.
Application programming interfaces (APIs) exist for:[18] Recent frameworks such as Ruby on Rails, Catalyst, Django, Kepler and Plack allow use with either the embedded interpreters (mod_ruby, mod_perl, mod_python or mod_lua, for example), or FastCGI.