Viktor Isaev
Viktor Isaev
@ryardley, yeah, of course - there will be an abstract interface and the actual transport will be pluggable.
Is this due to lack of message durability? Just to make it clear, what features that Kafka/RabbitMQ provides are you missing?
Yes, there is often a tradeoff between flat clustering with message bus (we can name it "microservices") and hierarchical clustering with direct messaging (we can name it "actors"). Each has...
Yes, that's right. Comedy allocates a dynamic port for each remote actor and does direct messaging between parent and child through this port. We could implement an option of proxying...
Hi @rijnhard ! Thank you, that's a very good point! I'll implement that on weekend.
I've released a quick fix for Winston as you mentioned. The fix is available in version `2.1.4`. The logging configurability feature is still to come. #61
@rijnhard Well, the fix was trivial and you did 100% of the research yourself! :) The logging configuration functionality won't arrive that fast, I'm afraid :) But that's a needed...
Yeah, looks like a nice enhancement.
Actually, this functionality can be easily implemented using the following code: ```javascript let actorSystem = actors({ config: `./actors-${process.env.COMEDY_MODE || 'prod'}.json` }); ``` I don't think we need something more complex...
Same problem with Russian "б". I need to try your fix.