Difference between revisions of "Structural Design Overview"
Zero Linden (talk | contribs) m (Proposed Architecture moved to Structural Design: refitting in with new AWG document layout) |
Rand Linden (talk | contribs) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:AWG_NavBox}} | {{Template:AWG_NavBox}} | ||
[[Image:slarch.jpg]] | [[Image:slarch.jpg]] | ||
In [[ArchWG_Mtg_1_Agenda|Meeting 1]] Zero Linden was giving a small overview of how Linden Lab is thinking about a new architecture for the Second Life grid. | In [[ArchWG_Mtg_1_Agenda|Meeting 1]] Zero Linden was giving a small overview of how Linden Lab is thinking about a new architecture for the Second Life grid. | ||
| Line 40: | Line 41: | ||
[[Category:Architecture Working Group]] | [[Category:Architecture Working Group]] | ||
[[Category:Grid_Interoperability]] | |||
Latest revision as of 23:19, 28 April 2009
In Meeting 1 Zero Linden was giving a small overview of how Linden Lab is thinking about a new architecture for the Second Life grid.
These slides are also viewable in Second Life on the open source island Hippotropolis.
Today and Tomorrow
First a slide on how things work today:
Today the viewer only connects to the region and the region keeps track of everything and acts as a proxy to the central databases. With the numbers envisioned in Project Motivation the central servers will not be able to cope with that.
The solution Linden Lab sees is to divide the structure into an Agent Domain and a Region Domain, each of them handling the components they are named after. Moreover there are some more central services such as Identity, Location, Currency and Search and there might be the case that multiple domains need to work together.
Made decisions
- It will all be based on REST
- Certified HTTP will be used where appropriate (exactly-once messaging between reliable hosts). Implementation is ongoing.
- Capabilities will be used
- LLSD will probably stay on not be changed to JSON. According to Linden Lab this should be no problem as there is a library for most languages to handle LLSD.
Final example setup
If all this is implemented it might look like this in the end.