MAAS: MUD As A Service

[krem]

In my line of business (I'm a Web Development Manager), I deal with a whole host of new technologies coming (and going). One that I always found intriguing was the Web Service/Service Oriented Architecture (SOA) development model. In fact, one of my more important, and very visible to Upper Management, projects is a site that runs completely on Web Services to communicate and interact with legacy web apps. While the network traffic is higher for SOA style app, it's very scalable and easy to extend.

The other day I was thinking about this: MUD As A Service. What if the way MUDs are developed going into the future were not monolithic game engines/drivers with custom game libraries on them, but rather a core set of services that could interact with each-other. Of course, some standards would need to be written to provide a common communication, but it wouldn't be difficult to get together.

It's something that I need to think more about, but I thought it was intriguing...

[mrfr0g]

Interesting concept. You could feasibly connect multiple game engines together to form a "super" game.

[York]

Software As a Service was one of the reasons I chose Erlang. If your going to run service through the web using SOAP or AJAX your going to want something that scales.