comedy
comedy copied to clipboard
untu
Node.js actor framework.
It would be great to set different config for `development` `test` `production`. What do you think about this?
Hello! I'm starting a new project with TypeScript and currently experimenting with Comedy as a solution for scaling the application. I ran into an issue with the way Resources are...
When I run tsc, the compiler tells: > xxx/AppData/Roaming/npm/node_modules/typescript/lib/lib.es2015.iterable.d.ts:41:6 - error TS2300: Duplicate identifier 'IteratorResult'. > > 41 type IteratorResult = IteratorYieldResult | IteratorReturnResult; > ~~~~~~~~~~~~~~ > > node_modules/@types/node/index.d.ts:165:11 >...
See [this issue](https://github.com/untu/comedy/issues/5#issuecomment-273021713) for more context.
Implement automatic actor scaling up and down according to the load.
When launching remote actor for testing purposes, it's often convenient to specify SSH credentials rather than deploying comedy-node on remote machine by hand. Comedy should support this.
Implement an actor mailbox size limit capability. This way, a user will be able to avoid overloading actors with too many messages.
For now Comedy uses simple point-to-point channels for message exchange. There should be an option to use Kafka message broker as an underlying transport for more advanced and robust messaging.
For development and debugging purposes it may be useful to transfer logs from remote actor to a parent actor to see the full picture of an actor system in the...
When a message is sent through a balancer actor to a cluster actor that crashes, the balancer should attempt to re-route that message to another actor in the cluster. The...