[KLUG Members] MySQL adoption

[Adam Williams]

>>> MySQL is great as long as you don't mind doing the work in the 
>> application code rather than in the db. That is really what it comes 
>> down to. For the small PHP apps I write MySQL is great. One day I might 
>> get into a project large enough that I need the separation.
>Makes one wonder why Sabre is using MySQL.  They aren't following that 
>logic (small => mysql, big =>postgres).  Sabre is big (two billion in 
>revenue last year) and they went with MySQL.

Well, big != PostgreSQL.  Big usually = Informix/Orable/DB2 because the 
management tools are *SO* much better.  I'd wager they plunked down some 
cash for some nice backup & snapshoting solution;  and it still might have 
been cheaper than a DB2/Orable license agreement.

And I'd wager real money that Sable is a multi-tiered solution with a 
business logic tier,  in which case the technological requirements on the 
database may be greatly reduced (it isn't bieng asked to be anything other 
than a database).

>Their project is described as "mission-critical enterprise services that 
>conduct online travel searches for Sabre Holdings customers such as 
>Travelocity, airlines and travel agents worldwide."
>http://www.mysql.com/press/release_2003_33.html

Notice that it doesn't mention anything about integrating with their 
business system (accounts receiveable, payable, etc...), primarily this is 
driving an Internet/Intranet application (albiet a BIG one,  but the 
<i>vertical</i> (i.e. more connections) scalability of MySQL has never 
been whats in question).

A more technical analysis as to how they interact with other systems 
would be much more enlightening.