Fork me on GitHub
#aws-lambda
<
2017-09-14
>
mj_langford17:09:51

I'm not sure Lambda is the best tool for that, but I've done stuff in that area @lucasbradstreet

lucasbradstreet17:09:44

@mj_langford we agree. We’re considering working on a feature that would move the complex event processing logic to an external service, and then leave Lambda purely for processing the final decisions (i.e. side effects)

mj_langford17:09:05

Amazon Step Functions do that kind of thing btw

mj_langford17:09:37

(depending on how complex your patterns are)

lucasbradstreet17:09:46

We looked into them, and they appeared to be more useful for workflows with action dependencies, whereas we are thinking about use cases like: if event type A and event type B over threshold y arrive, perform a side effect. These kinds of data dependency questions seem pretty hard to do with step functions

lucasbradstreet17:09:57

Does that match your understanding?

mj_langford17:09:26

Oh, yeah, that kind of thing is more of a queue problem IME

mj_langford17:09:39

and that's not Step Functions thing

lucasbradstreet17:09:48

Great, that’s basically what we think too, and once you have a queue then you need to keep some state somewhere, so you can decide whether the events you’ve processed have met the criteria.

lucasbradstreet17:09:56

Thanks for your thoughts