||This article has multiple issues. Please help improve it or discuss these issues on the talk page.
|Original author(s)||Sebastian Riedel|
|Stable release||5.90030 / 12 April 2013|
|Type||Web application framework|
|License||PAL and GPL|
Catalyst is an open source web application framework written in Perl, that closely follows the model–view–controller (MVC) architecture, and supports a number of experimental web patterns. It is written using Moose, a modern object system for Perl. Its design is heavily inspired by such frameworks as Ruby on Rails, Maypole, and Spring.
A web application developer would use Catalyst to deal with code common to all web applications: it provides interfaces to web servers and receiving page requests, dispatching these into developer-written code to process and return the requests, and provides a standardised interface for data models, authentication, session management and other common web application elements.
All of these elements are implemented as plugins to a set of common interfaces, allowing the developer to change the specific method used (e.g. a session storing in shared memory versus as a database table, or using FastCGI versus operating as an within Apache's mod_perl) by changing the configuration of Catalyst to use a different plugin without altering the application code.
Catalyst is primarily distributed through the CPAN, which is the official distribution channel for Perl libraries and applications.
Catalyst started as a fork of the Maypole framework. Its first development release took place on 28 January 2005. The first official version hit CPAN on 16 February 2005. As of June 2011, Catalyst had 201 registered contributors.
Catalyst is based on a "don't repeat yourself" (DRY) principle, which means that definitions should only have to be made once.
Catalyst can be used with automatic class loading from the database through one of the many loader modules, thus requiring no code for the database layer. But, if you require the flexibility of manually doing everything, it's also an option. Another guiding principle of Catalyst is flexibility.
Catalyst promotes the re-use of existing Perl modules that already handle common web application concerns well.
- The Model part is handled through DBIx::Class, Plucene, Net::LDAP and other model classes.
- The View layer is usually handled by Template Toolkit, Mason, or HTML::Template, among others.
- The Controller layer is of course written by each application author. Large chunks of Controller functionality can usually be deferred to one of the many Catalyst plugins (e.g., Catalyst::Plugin::FormValidator, Catalyst::Plugin::Prototype, Catalyst::Plugin::Account::AutoDiscovery, etc.).
- Finally, Catalyst offers a set of helpers to simplify flow control and mapping URLs to controller methods.
Web server support
For development and testing, Catalyst has a built-in simple HTTP server. For production use, Apache, lighttpd, Hiawatha, Cherokee or Nginx with FastCGI or mod_perl support is recommended, but any web server with CGI or FastCGI support will work. On Apache, mod_perl can help with performance considerably, though its use might be an issue because it can be unsafe to share multiple applications under mod_perl.
Since early 2008, Catalyst applications can also be deployed using the HTTP::Prefork engine which provides for the deployment of high performance Catalyst applications without a separate web server.
Starting with the release of Catalyst 5.9, Catalyst also outputs to the PSGI spec thus it can be run on any Plack server and along with any server or protocol that supports the PSGI spec, including Mongrel2.
Catalyst can run using any database supported by Perl's DBI (this means almost anything, even a CSV file), but a proper RDBMS or ODBMS is recommended. The database access is entirely abstracted from the programmer's point of view and Catalyst, through one of its model classes, handles access to all databases automatically – though, if needed, using direct SQL queries is possible. This enables database-neutrality, application portability over different database systems, and usability of pre-existing databases for Catalyst application development as much as possible, though due to different feature sets of the RDBMSes, it is not completely guaranteed by the framework alone. Several different RDBMS systems are supported, including MySQL, PostgreSQL, SQLite, IBM DB2, Oracle and Microsoft SQL Server. For ODBMSes, there is explicit support for KiokuDB via Catalyst::Model::KiokuDB. The Model abstraction allows databases of any nature to be accessed via Catalyst::Model::Adaptor.
Many Catalyst-based projects use DBIx::Class as the ORM layer, which provides further abstraction of SQL queries, using a resultset-based API with transparent support for arbitrary joins and other features.
- Diment, Kieren. The Definitive Guide to Catalyst. Apress. ISBN 978-1-4302-2365-8. Retrieved 2009-09-09.
- The Definitive Guide to Catalyst. Apress. p. 2. ISBN 978-1430223658.
- Catalyst Changes file
- "Catalyst Framework - Contributors". Ohloh. Retrieved 2011-06-06.
- large selection of plugins
- HTTP::Prefork engine
- "Biggest porn site on the web YouPorn powered by Perl/Catalyst (top 50 in alexa)". reddit.
- ""Catalyst/DBIC/eCommerce Developer job" posting". 2011-05-08. Archived from the original on 2011-06-06. Retrieved 2011-06-06.
- Diment, Kieren; Trout, Matt S (2009). "Catalyst Cookbook". The Definitive Guide to Catalyst. Apress. pp. 278–281. ISBN 978-1-4302-2365-8.