I've been pondering a similar question myself. In my case, I'm developing a web app that will function as an online store-front, complete with user login, shopping cart, etc. So, basically every page hit is going to generate lots of database queries (session data, such as, is the user logged in? do they have items in their cart? as well as pulling items out of the inventory database for browsing). This is all great, in theory, but my web host provider has strict rules and regulations regarding how many computer resources one can use in a given month (disk, cpu, bandwidth, database access, etc.) I'm worried that I may go over my db limit with the current all-mysql implementation, so I'm considering using sqlite, or db_file, or something similar, that looks like a database in my code, but is really just a file on the server. This might work fine for small tables, sessions ids, etc. I've never seen anyone discuss issues related to partitioning up data this way, but I'd imagine it comes up frequently in practice, in shared hosting environments. In your case, sqlite might make sense in *some* areas, if not all.

In reply to Re: SQLite3 use in production by scorpio17
in thread SQLite3 use in production by Akoya

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.