What hard-core transactional applications have actually been built in MySQL, PostgreSQL, EnterpriseDB, or FileMaker?
And here’s the biggie.
Question of the day #3
What complex, high-volume transactional applications have actually been built in mid-range DBMS such as MySQL, PostgreSQL, FileMaker, or EnterpriseDB?
I’ve been flamed for suggesting that MySQL or FileMaker aren’t fully equal to Oracle and DB2 in supporting hard-core transactional applications. (Which is ironic, because I’ve also been flamed for suggesting hard-core transactional support isn’t as big a deal for DBMS selection as some relational purists insist. But I digress …) So I’m putting the question out there — what impressive transactional applications do the stand-alone mid-range DBMS actually support?
We can’t ask that question of the crippled editions of Oracle, DB2, et al.; it would be too hard to sort out from the apps running on their high-end versions. We needn’t ask the question of Progress and Intersystems; their reseller catalogs give the answer. We certainly needn’t ask it of MaxDB; it runs a significant fraction of the SAP user base. But for the four DBMS I named, I think it’s an interesting challenge.
Specific information I hope you’ll provide includes:
- Peak load of concurrent users.
- Peak load of transactions/second and/or updates/second.
- Metrics for the complexity of the database (e.g., number of tables).
- How intensely the application uses triggers, stored procedures, and/or declarative referential integrity.
- Any other metrics you think are impressive or relevant.
My logistical suggestions for supplying examples are as per Question of the day #1.