AlpacaGoesCrazy

Waiting for 100 events is not suitable for real time application, you can not even estimate message delivery estimate. And about using EC2 instance to process events, this might be...

@eduard-malakhov The architecture idea of this project is to communicate subscription message from one source to multiple subscribers in a fan-out fashion. The publisher lambda in dynamoDB implementation is responsible...

@eduard-malakhov I think my original idea was to dynamically create an SQS queue per one subscriber for achieving message delivery guarantee, I am not sure if it will be possible...

> Do you mean to send event "manually" by invoking the lambda with this event? Or do you mean to process the event directly in the same process? I mean...

> How is event processor logic tied to mutation except that you need to publish an event somehow? I think this is the only case > If you invoke such...

> The problem in both cases is if you receive an event and then you need to send it to multiple connections and it fails in the middle. It'll cause...

> For example let's say that you're developing a chat app with rooms. Now you subscribe to `RECEIVE_MESSAGE` but it's too general. You want to subscribe to messages from specific...

> Yes I like the idea you proposed only thing is that it's not compatible but that can be addressed for example by introducing new package for this type of...