
"EVE Online's complicated inter-corporate politics are often held together by fragile diplomatic treaties and economic agreements. So fragile, in fact, that
a single misclick can lead to a fracas that quickly snowballs into all-out warfare. That's what happened to two of the spacefaring sandbox MMO's largest player alliances in the Battle of Asakai, a massive fleet vs. fleet onslaught involving 3,000 players piloting ships ranging from small interceptors to gargantuan capital ships. Straight from the wreckage-strewn outcome of the battle, we're breaking down the basics of what happened for everyone to truly fathom one of the biggest engagements in the game's history." The costs of this battle in in-game currency is, so far, 700 billion. While MMO's don't float my boat, I have to say that this is still pretty awesome. Penny Arcade
looks at the technical details server-side, and what a battle like this does to the game's backend infrastructure.
Member since:
2005-11-16
Hi,
Traditional MUDs... no. But there was some effort to make distributed system of MUDs. "
I was looking at wikipedia's list of "distributed computing architectures":
http://en.wikipedia.org/wiki/Distributed_computing#Architectures
You'll see that boring old "client-server" (potentially including one client on one computer talking to one server on a different computer) is the first architecture on their list.
In my opinion, boring old "client-server" (including multiple clients talking to one server, and multiple clients talking to multiple separate servers) is just client-server and doesn't really qualify as a true distributed system.
Now; EVE Online (as I imagine it) is a slightly more complex case of client-server. I'd imagine that each individual client is talking to at least 3 different servers (one for chat, one for the economy/trade, and another for "objects in space"); but despite this it's still all just client-server, and still doesn't really qualify as a true distributed system in my opinion.
These are all practical considerations only (e.g. shared state and/or heavy communication tends to kill scalability/performance; and local independent datasets is the result of minimising shared state and communication).
What does qualify as "true distributed" is when multiple computers work together, rather then independently. Google (many computers working in parallel for each query), Wikipedia (front-ends, caches, databases, media servers, etc for each page request), BitTorrent, SETI@home, supercomputers.
- Brendan