On the contrary, I'm unable to to think why relational database server (or embedded solution) would be
a) more reliable
b) faster
c) easier to maintain
d) faster to develop
e) cheaper
f) use less resources (RAM)
than hard-coded perl module. This data is static, and seldom changes (once a year?).
The thing is that we do need network based (e.g. HTTP) lookups for other server to make, but even more important is some kind of library (a module that is), that will be used by other (perl) scripts (web and backend) for batch processing.
E.g. a CSV file with 50k phone numbers to be imported over the Net, and processed. IT doesn't make sense to do SQL query for each single number. A library module is needed.
Also, we simply do not use relational DB server for this project, and it's not worth to set up one, just for these lookups.

In reply to Re^2: large perl module by minek
in thread large perl module by minek

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.