/goblins/concept/index.html The goblin idea match perfectly with the actor model of Carl Hewitt designed in 1973. We don’t know this model before designing this framework, after some search on wikipedia we discover that our work match the following definition perfectly. The actor model in computer science is a mathematical model of concurrent computation that treats actor as the universal primitive of concurrent computation. In response to a message it receives, an actor can: make local decisions, create more actors, send more messages, and determine how to respond to the next message received. Hugo en-us /goblins/concept/overview/index.html Mon, 01 Jan 0001 00:00:00 +0000 /goblins/concept/overview/index.html Goblins use xcraft messages to send command’s and event’s to others, example: //somewhere in the codebase of a goblin... function*(quest){ yield coolGoblin.doSomething({content: 'Hello Goblins!'}); } And in response, the cool goblin can say something with a hypotetic vocal synthetizer goblin: //somewhere in the codebase of a the coolGoblin... //In response to a message it receives... doSomething = function* (quest, content) { //create more actors const myCoolSynthAPI = quest.create('synth-goblin', { id: 'synth-goblin@cool-goblin', }); //use API for doing side-effects yield myCoolSynthAPI. /goblins/concept/atyourservice/index.html Mon, 01 Jan 0001 00:00:00 +0000 /goblins/concept/atyourservice/index.html For building the application you dreamed, you will ask yourself some right questions: my app will run for a single user in his device ? my app will run for a myriad of users, on a server ? In all case, the crucial point is, my app is in all case a server hosting some “little know” services, aka goblins! Don’t worry, if you choose xcraft and goblins for your next app, you can fit a lot of deployment configuration and topology. /goblins/concept/quest/index.html Mon, 01 Jan 0001 00:00:00 +0000 /goblins/concept/quest/index.html Every app has a beginning and an end. What lies between those two points is the quest For defining goblin capabilities, we register a quest to the central agency of all goblins, that finish in the chief Orc xcraft bus commands registry. A goblin with a quest named killJohnFitzgeraldKennedy can certainly make a killer feature… We register a quest for goblin-oswald aka the service name of all instances We name the quest We provide a function or a generator receiving the quest context in first argument We expect to receive a message containing a date and a place for doing our work Goblin.