Your Amazon Prime 30-day FREE trial includes:
| Delivery Options | ![]() |
Without Prime |
|---|---|---|
| Standard Delivery | FREE | From £2.99* |
| Premium Delivery | FREE | £4.99 |
| Same-Day Delivery (on eligible orders over £20 to selected postcodes) Details | FREE | £5.99 |
Unlimited Premium Delivery is available to Amazon Prime members. To join, select "Yes, I want a free trial with FREE Premium Delivery on this order." above the Add to Basket button and confirm your Amazon Prime free trial sign-up.
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, you will be charged £95/year for Prime (annual) membership or £8.99/month for Prime (monthly) membership.
Buy new:
£44.99£44.99
Dispatches from: Amazon Sold by: Amazon
Save with Used - Very Good
£3.86£3.86
FREE delivery 14 - 16 August
Dispatches from: awesome_books_001 Sold by: awesome_books_001
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
The Definitive Guide to Catalyst: Writing Extensible, Scalable and Maintainable Perl-Based Web Applications (Expert's Voice in Web Development) Paperback – Illustrated, 9 July 2009
Purchase options and add-ons
- ISBN-101430223650
- ISBN-13978-1430223658
- Edition1st ed.
- PublisherApress
- Publication date9 July 2009
- LanguageEnglish
- Dimensions17.78 x 2.08 x 23.5 cm
- Print length390 pages
Product description
About the Author
Product details
- Publisher : Apress; 1st ed. edition (9 July 2009)
- Language : English
- Paperback : 390 pages
- ISBN-10 : 1430223650
- ISBN-13 : 978-1430223658
- Dimensions : 17.78 x 2.08 x 23.5 cm
- Best Sellers Rank: 3,663,643 in Books (See Top 100 in Books)
- 5,091 in Internet Applications
- Customer reviews:
About the author

Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings, help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from United Kingdom
There was a problem filtering reviews right now. Please try again later.
If you want to use it to discover Catalyst and analyse the engine. I'd propose another solutions, cheaper and faster. Just the web.
Looked like an updated variant of "Catalyst Accelerating Perl Web Application Development", but had so many errors, so I went back to the original.
Pity
Top reviews from other countries
After spending a couple of days with Catalyst, I decided that it would be difficult to develop and document with an existing code base. I am fighting with about 80K lines of code written over a ten year period. I needed to develop a framework to allow the code to grow with demands on the system. I did not feel comfortable that I could use Catalyst around the existing code and to build a framework for the long run. I feel much more comfortable building a solid class structure that I can add incrementally to the existing code and take the code to the next level. So, I am back to some of the more basic CPAN packages and am focusing on good design.
I was hoping this book would act as a reference manual so that I could get a view of the internals and functionality. However, it does not seem to be organized in such a way. That being the case, I suggest that you check out the tutorials online to make a decision if you want to use Catalyst. If you decide on Catalyst this book's tutorial style, you will find it is a good book that provides solid examples, good design methods, information on databases and lots of basic software design discussion and comments on style.
Doesn't anyone in this business hire proofreaders? Virtually every code sample presented in the first three chapters has at least one error (c'mon people, there's a difference between one underscore and two, right?).
And I'm sure the authors are fine programmers, but they're dreadful writers of expository prose. This book is just begging for a mile-high overview explaining, in general terms, what the various MVC components do and how they fit together. Instead what we get is a brief, jargon-filled tour of these concepts, followed by a leap into an error-filled sample application. (At first I dutifully noted every error but gave up midway through Chapter 4.)
I can easily forgive poorly written documentation when the people writing it aren't being paid for their effort. But when I pay $30+ for a book, I expect the publisher to have at least proofread the thing.
By the way, I'm not a complete Perl noob. I've been using it for several years and have benefited greatly from the generosity of the many good folks who have contributed code to CPAN. To them, I am grateful; to the authors of this book, not so much.
*It earns one star simply for being a book on Catalyst.
UPDATE (June 11, 2013): I'm working through the book a second time, after having read the Catalyst manual and worked through the Catalyst tutorial on CPAN. It's even worse this time around. The number of errors is atrocious, and many of them are obvious to anyone paying any attention (e.g., a module identified on one page as DBAuthTest::Controller::AuthUsers is referred to as DBICTest::Controller::AuthUsers just a few pages later). The code samples in the book often don't even agree with the archived code provided on the publisher's Web site. And the authors make no use of graphics to illustrate the complex relationships between the various MVC components. Worst of all, the publishers obviously didn't bother to proofread or edit this book. Even the grammar is poor in places. So I've requested a full refund. The book may be useful at some point as a reference for "best practices," but it's nothing but frustration as a learning tutorial.
Perl 5 core has been stable for quite some time. However modules and usage have evolved. Even if you don't plan to use Catalyst, read this book for the peripheral knowledge the book pulls in.
For example, I was pleasantly surprised to see nginx mentioned as a potential Web server to use. This to me meant that the book is not a quick job done by an author gathering materials over the web, but a labor of love written by somebody who has hands on experience with the modern Web.
Unfortunately, I found this guide a disappointment as well. Most of the book seems to be structured around a few "examples," the largest of which is a translation app from English into "Lolcat." The problem with such an app as an example is that it could readily be done in a dead-simple, several-line CGI script (hell, even a one-liner could probably do it), so it requires a certain suspension of disbelief that one should be using stashes, chained dispatch methods, templates, and the like. Why not a normal CRUD type app as an example? Boring, yes, but to-the-point and more likely to be illustrative of the tools and their best applications.
The conversational "flow" of the book is distracting, as well. I understand that a more tabular or outlined form for making specific information easier to find could render it hard to read "straight through" as a book. But the sheer volume of information, and diversity of scenarios, make it unlikely that anyone will read it straight through and make equal use of all parts. Far better to organize the content more rigorously by function -- for example, the best and best-structured chapter by far is the chapter on dispatch (it gets to borrow for its prose structure from the flow chart on page 168. Less in-depth meanderings into such adjuncts as DBIx::Class and Moose, but more on how (if at all) such outside modules must interface / play nice with the Catalyst core. A chapter on errors. A chapter on logging. A chapter on templating.
The index is a mess and lazily put together. Under "log", only one entry: "Logging, in Catalyst, 7." (Are you serious? who wrote that index entry? Logging, comma, IN CATALYST?!? SERIOUSLY??) For "error:" "error handling code, changing to output errors to the log, 104-105." Nothing for "exception" (fair enough, as Perl properly has none), but under Perl's equivalent, "die:" "die, using for error handling, 156." WTF? Finding these three sections shouldn't be an Easter-egg hunt. WTF would be wrong with:
error
using "die" ... 156
logging ... 104-105
see also *log*
log ... 7
errors ... 104-105
I'm rooting for Matt & co., and I'm a fan of Catalyst. But this book needs a reworking for its next edition, and it needs an editor (the typography, too, is underwhelming). It's not that the team that wrote this isn't smart enough, or that they don't know the subject well enough. It's merely that they need to structure, structure, structure, and clarify, clarify, clarify. Looking forward to second edition, guys.
