My experience and training have hammered home the point that Decision Support (DSS) and On Line Transaction Processing (OLTP) present different challenges and loads on database servers.

All DSS, which is read-only, really needs is good indices, logical, and physical design. A lot of RAM allocated to the data cache helps, since reading from cache is a whole lot faster than reading from disk.

OLTP, on the other hand, needs to assure data integrity while rows are inserted, deleted, and modified. Triggers, declarative constraints, procedures, rules, defaults, and transaction processing with commits and rollbacks all come into play here, and this takes cpu cycles and well as physical reads and writes to the database.

Concurrency and data integrity, thus, are often at loggerheads when it comes to database design. We have here the "2 out of 3" principle in operation:

You can have it quickly;
You can have it cheaply;
or you can have it right --

But you can only have two of the three.

MySQL excels at DSS applications, but a production database where data integrity is crucial needs more than MySQL is able to offer. We use a full-featured RDBMS for our production databases, but several smaller applications are using MySQL. It's a question of using the appropriate tool for the job.

-----
"Computeri non cogitant, ergo non sunt"

In reply to Re: exploring XP DBI DBD DBM SQL RDMS MySQL Postgres by cadfael
in thread exploring XP DBI DBD DBM SQL RDMS MySQL Postgres by mandog

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.