Ivan Zhuravlev

@icebob if I understand correctly, in this way we will also solve the problem with tracing, since stream will no longer be in the context of the default parameters that...

Because NATS server can run a WebSocket server out of the box, implementing a specialized transport will be redundant. In addition, there are already several modules for WebSocket under Moleculer....

> For instance, service A can call service B on startup, waiting for it, if needed, but without blocking the start of service A. Maybe the asynchronous method on events...

Why not `use ctx.call()` in this example (user registration) and get not only confirmation, but also other features of the built-in middleware?

For such tasks, I also want to see a built-in task queue in the moleculer protocol and an internal service. Many things have already been implemented for it and are...

Now I will make and add tests

The preliminary result is that simply sending the request through master will not work. I'm figuring out if this problem is related to my tests or it's a bug in...

@JordanPawlett 1. You could clarify how exactly your cluster is assembled through sentinel or redis cluster 2. Its configuration is how many masters and slaves per master. 3. And is...

> If i remember correctly the Redis discovery worked correctly with a Sentinel setup. However, breaks for redisCluster, as `scanStream` does not exist on that client. Sentinel works differently, unlike...

> Any news about it? Alas, I don't have a solution yet. In testing, I didn't a solution with `client.nodes ('master')`. I will run tests again with the current versions...