Re: MySQL as a production server - Dirk Hillbrecht - com.mysql.lists.java

8 messages in com.mysql.lists.javaRe: MySQL as a production server

From	Sent On	Attachments
Matt Goss	10 May 2001 06:01
Dirk Hillbrecht	10 May 2001 11:16
Pance Stojkovski	06 Jul 2001 11:13
Dirk Hillbrecht	07 Jul 2001 03:14
Igor Fedulov	10 Jul 2001 14:15
Igor Fedulov	10 Jul 2001 14:37
Igor Fedulov	10 Jul 2001 14:55
Igor Fedulov	10 Jul 2001 14:57

Subject:	Re: MySQL as a production server
From:	Dirk Hillbrecht (dh...@chitec.de)
Date:	05/10/2001 11:16:01 AM
List:	com.mysql.lists.java

Hi all,

Am Donnerstag, 10. Mai 2001 15:02 schrieb Matt Goss:

Does anyone have any examples of MySQL being used in as a production server??? Is it recommended???

Ok, so what am I myself doing? I am developing a car sharing booking system with addons (like interfaces to access systems in the cars which allow access only after a booking has been placed and must therefore be informed about bookings). This system is a three tier application with Java server application, Java client applications, Web interface etc. Currently, we have six servers up and running, the oldest one set into operation in early 1998. Together, they serve about 680 cars and over 13000 users, which is the largest booking software installation on the German carsharing market.

The largest of our server has approx. 200 of the cars and now over 100.000 bookings in its databases (we don't delete them). Everything everywhere runs on MySQL, of course. The hardware is standard PC, Pentium II/300 up to Pentium III/800, 128 MB of RAM or more.

Of course, we had one or another problem with the installations over the time (we do updates rather frequently to insert new features). The only component which never ever made a single problem on any installation was - MySQL. It runs absolutely flawlessly - you install it, you start it, you forget about it. It's simply there. Search time on the booking table is more or less indepentent of the size - it doesn't matter whether the table has 1000 rows or 100.000 - as long as you care about appropriate amount of RAM...

Ther are, however, some limitations. One really nice thing would be foreign key handling, but, hey, it works without, also. For certain features (e.g. row locking), I developed helper classes which made it available. Other features like transaction handling were not available when I started development (back in 1997), so my application was designed a way where it wasn't needed. Somewhen in the future, we will use the quite new replication mechanisms to maximize fault tolerance.

All in all I am really really satisfied with MySQL. I would not hesitate to use it again in an equally shaped project, and I would suggest for everyone else to do so, too.

Ciao, Dirk