We like our new web server. It’s now being used for hosting Hyzonia.com main website and the Core. The migration of files, websites and settings from the old server to this new one was very smooth, honestly I was expecting us to have a big headache in moving a complex web app like Hyzonia, but so far it’s working flawlessly.
The features that we have developed to make Hyzonia network more scalable played a big role in making this transition easy and smooth. The nodes, parts and modules of the application use web services to communicate with each other and clearly when we have web services it really doesn’t matter where those parts reside in; during this migration we were able to move modules individually. On the other hand we’ve used provider pattern aggressively in the codes, hence features can have multiple implementations and switching among these different implementations is very easy and immediate. Using all these things, if a module goes down because of the new environment, somebody can connect the app to the old module (a web service feature) or configure the app to use another, more stable implementation of the module.
Similarly a third party developer who wants to develop a new game for Hyzonia has two options:
- Consume web services
- Create new implementations for some abstract functionalities
(Actually there’s a third way, somebody can customize an existing game, it’s cool and exciting but I’m not counting it as a new type of game)
In this blog we will focus first on the easier option that is using web services. All the functionalities that Hyzonia provides for games are available as part of web services, and here we will gradually talk about them.
Right now we are working with a small community of developers to fine tune the APIs, drop us a message if you are interested too.
0 comments:
Post a Comment