Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (781)
Games in Android Showcase (233)
games submitted by our members
Games in WIP (857)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  Concurrency Library 2.0  (Read 1733 times)
0 Members and 1 Guest are viewing this topic.
Offline DrakosKai

Senior Newbie

Medals: 3

« Posted 2016-04-14 14:57:29 »

Last year I wrote up a post on the Disruptor pattern and solicited some general opinions about it's potential application in gaming.

Since then I've been working with Apache Storm and at its heart it uses the Disruptor.  Storm uses the disruptor in a way that wasn't originally defined by it's creators.  Storm can process an incredible volume of data distributed over multiple servers.

The queue itself is called by Clojure code so it's not directly obvious in the java how it's implemented. Sad

I've been thinking: "What if you could create a game server cluster that shared the workload of updating the world?"

Offline Varkas
« Reply #1 - Posted 2016-04-15 13:06:26 »

I've been thinking: "What if you could create a game server cluster that shared the workload of updating the world?"

Once, I think this is already done. Large scale business applications work on clusters with shared data, scientific applications as well, so I'm pretty sure games can do that, too.

Second, the only effect is that you can run larger worlds with more players, and have less need to separate regions into instances. Instances can always be distributed among a cluster easily, since they are isolated from the rest of the games world.

I don't think it will be a very fundamental change. Instances may be partly driven by technical constrainst, but for most multi player games they are also required for gameplay reasons - players in different stages of the game need to experience different views on the world, and this is usualyl done by providing instances that fit the "story progress" of the characters - e.g. the change of before and after a quest has been completed.

if (error) throw new Brick(); // Blog (german):
Pages: [1]
  ignore  |  Print  

hadezbladez (1165 views)
2018-11-16 13:46:03

hadezbladez (525 views)
2018-11-16 13:41:33

hadezbladez (1187 views)
2018-11-16 13:35:35

hadezbladez (272 views)
2018-11-16 13:32:03

EgonOlsen (2567 views)
2018-06-10 19:43:48

EgonOlsen (2786 views)
2018-06-10 19:43:44

EgonOlsen (1564 views)
2018-06-10 19:43:20

DesertCoockie (2269 views)
2018-05-13 18:23:11

nelsongames (2121 views)
2018-04-24 18:15:36

nelsongames (2815 views)
2018-04-24 18:14:32
Deployment and Packaging
by philfrei
2019-02-17 20:25:53

Deployment and Packaging
by mudlee
2018-08-22 18:09:50

Java Gaming Resources
by gouessej
2018-08-22 08:19:41

Deployment and Packaging
by gouessej
2018-08-22 08:04:08

Deployment and Packaging
by gouessej
2018-08-22 08:03:45

Deployment and Packaging
by philfrei
2018-08-20 02:33:38

Deployment and Packaging
by philfrei
2018-08-20 02:29:55

Deployment and Packaging
by philfrei
2018-08-19 23:56:20 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!