I have never implemented this in Perl, and I am a Perl newbie, but have been programming in other languages for a few years. If someone else mentioned this then, sorry, I didn't understand it.

A common method of abstracting the database layer in other languages is to implement a class(module) that contains all database access code. This class acts as a mediator between your application code and the database. Do you need to get some user information from the database, call a method of the db class. How about updating the users information, call a method of the db class, etc... This provides the following benefits:

One pitfall is the added complexity. I have found debugging this type of architecture is more complicated than its flatter counterpart; but I think the benefits normally outweigh the consequences.

I would be interested in knowing if anyone has implemented this in Perl and how it worked out for them. Even if you haven't implemented it, I would like to know if there are any reasons why this wouldn't be w good idea in Perl (I will be considering this architecture in the near future).

-disciple

I am not even sure if it is appropriate that I attempt to comment on your post. It would seem to me that you probably already know what I wrote.


In reply to Re: Performance v's Maintainability by disciple
in thread Performance v's Maintainability by Ryszard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.