SL's back end?

This isn't an issue, perse, but I couldn't think of a better place to post it.

What database software does SL use on it's backend? Is it MySQL, Oracle, DB2, or something else? Homegrown maybe? I was reading an article about MySQL, and they mentioned an MMO that used MySQL for it's game. That kind of spun my brain off, wondering what backend SL used.

Thanks.

I have noticed this too. Sl's back end has definately 'filled out' quite a bit lately. Time for a diet and some exercise I think.

I was just WAITING for someone to say that.

I think I read somewhere (like in these forums) that it was MySQL. All of the ones you mentioned are of course SQL based, so switching from one to another wouldn't be too hard. They could even use Microsoft's SQL Server. *gah* The now mentioned four are constantly jockeying for market share in general and they each have niche markets. People forget though that SQL based databases were never performance champs.

As with so many other areas of computing, performace became less of an issue as the hardware got both faster and cheaper, so switching to something that was easier to set up and use regardless of performance became the norm, making products such as:http://www.cca-int.com/prodinfo/m204.html (Model 204) relevant for only very specialized applications.

I think I read somewhere (like in these forums) that it was MySQL.

That would seem to fit with their style -- Python, Perl, Linux, OpenGL, and C; all open source tools. Thanks!

I... like... big... db's and I cannot lie
You other geeks can't deny
And when a game goes gold with a speedy database and MySQL in your face
You get sprung!

Where are they using python and perl?
BTW, mac, switching from one DB to another isnt as simple as you may think.
There are many subtle SQL syntax differences between the various DBs, not to mention completely different stored procedure languages, and a horrible disparity on what features each db implements.

Where are they using python and perl?

I've talked with Phoenix -- many moons past -- and she mentioned they use it for log parsing, for one thing, that they had Python and Perl scripts they used. That most Lindens used Python, but they had one Perl guy there. (I'm recountiing a conversation from a while back, so there is a margin of error.)

I'd be surprised if they didn't use Python for handling some in-world logic (but that is my guess).

Ok. Now THAT was funny! haha.. Thanks Julian!

Yes, I'm familiar with the proprietary differences, however most of them support a core standard, and if you are carefull you can make your code portable.

I always advised my customers to pay attention to this, but few did. They pay for it later. Even within a particular implementation, for example from one version of Oracle to the next, it is those proprietary features that suddenly don't work the same, or at all. Most users, sadly, are locked into whatever SQL system they started with. All management has to do is instruct staff to avoid the non-ANSI stuff like the plague. But they don't. PHBs after all.

One good thing about MySQL though is that it is new enough that it doesn't HAVE a lot of the proprietary features (yet). My guess is that it would be a lot easier to go from MySQL to Oracle than the other direction.

All that being said though, it's still easier to switch from one SQL based system to another because they are all by definition "relational" (there are also relational databases that do not use the SQL syntax). After SQL started to catch on, almost all DBMS systems started advertising themselves as relational databases, but a few of them did this by simply imposing a relational layer on top of an existing hierarchical (for example) engine.

I don't follow the industry quite like I used to so I don't know how many of these companies are still in business, but I did remember Model 204 having a reputation as the fastest database engine by far for a while (which is why I mentioned them). I don't know if they can still claim that status. When companies like Oracle have an R&D department larger than your entire staff relative performance will suffer eventually. I helped run a benchmark a LONG time ago though and the Model 204 solution beat the Oracle solution by an order of magnitude, so it may well be that Model 204 is still enough faster to attract specialized applications. Relational is not a particularly efficient way to store data, the selling point has always been ease of use rather than how easy it is on your hardware.

Yes, mySQL is the database they use. I usually don't doubt my brain, but if you do, feel free to hunt down the various old threads about SL's infrastructure.

As for the filling out, more people are coming into the world, which brings more inventories available to hold obscure things that people forget to delete, so the SL weekly garbage collector doesn't get to do its job as well.