Wrap your database calls behind an API of some sort (OO is good here) and rewrite your application to think only in terms of these business-level function calls. So, instead of looking at it as "data from tableA and tableB", think of it as "the quarterly report data".
This has three benefits:
- Your application is more testable
- Your application is more agile when it comes to change
- You can change how the data comes to the application
#3 is the relevant one here. Once all your datastore access has been changed to be business-level, you can use SOAP, XML-RPC, HTTPS ... pick your favorite remote protocol to work with. Your application doesn't care. You can also handle more than one type of protocol, if your clients need this.
- In general, if you think something isn't in Perl, try it out, because it usually is. :-)
- "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.