Diogo Behrens

The storage is an interface, so you should be able to simply replace it with your extended version of the storage. Take a look in the [builders in `storage` subpackage](https://github.com/lovoo/goka/blob/21b04ba791d28c32ee85e8ef1682aea85d120b8c/storage/builders.go#L30)....

Good points. I'd be more than happy reviewing PRs for this issue and #77. If you'd like to try, please let me know. I can support you via chat if...

This would be awesome! We don't have use cases for that at the moment, but I'm happy to discuss about it. So `goka.Context` is an interface anyway. Whenever writing some...

Nice! I think it should be easy to wrap the callbacks in `goka.Input(topic, codec, callback)`. One idea would be to create a subpackage, say `timebucket`, then ```go g := goka.DefineGroup(...

I guess that was unclear. I'll write a longer example later today.

Ok, so the idea was to create a package, eg, `timebucket`. In this package we wrap the edges of the `GroupGraph` and redefine the `ProcessCallback` to use a more specialized...

We'd not be duplicating core functions. The functions I suggested should be seen as "builders" which wrap the original code with additional functionality. But other solutions are also possible. And...

That sounds really nice! It is simpler than my proposal above and should also solve your issue with joining two streams, right? Do you have a suggestion how to implement...

@burdiyan that sounds easy to implement. As far as I see, all these changes can be implemented on top of the existing edges. We just have to be careful what...

@andrewmunro you'll also need to keep track of what is the current month you are considering using a timestamp and then you'd have to reset the aggregation of the month...