Commentary

Mitch Wagner
Executive Editor, Community  

Exposing Second Life's Data Centers

Today InformationWeek undresses Second Life and leaves it naked and trembling. We lift up its skirts and peer at its naughty bits. We open up its dresser drawers and paw through its unmentionables. In other words, we go inside the data centers and describe some of the server and software technology that keeps the virtual world running.

Today InformationWeek undresses Second Life and leaves it naked and trembling. We lift up its skirts and peer at its naughty bits. We open up its dresser drawers and paw through its unmentionables. In other words, we go inside the data centers and describe some of the server and software technology that keeps the virtual world running.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

For those of you who are too hot and bothered to read the complete article, here are some highlights: The software architecture is an extension of the virtual world metaphor of Second Life. Each instantiation of the server architecture of Second Life controls a specific area of virtual real estate, and is assigned to a specific server, or a specific processor on a larger server. The server software -- called "simulators," or "sims" -- moves around, based on server crashes or downtimes. Still, at any time, it's possible to walk into one of Second Life's two data centers, pat one of the rack-mounted servers, and say that particular server is running virtual New York, or San Francisco, or ancient Rome.

Linden Lab, which develops and maintains Second Life, runs 2,000 Intel- and AMD-based servers in two co-location facilities in San Francisco and Dallas.

Read the article for more on Linden Lab's open source plans (although not too much more -- they're not saying much), and how Linden Lab is coping with the explosive growth of Second Life.

What else would you like to know about Second Life technology? Do you know any Second Life secrets you'd like to share with our readers?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links