Viktor Klang (√)

Actually, I figured it could make the transition from a stateless to a stateful function simpler 😊 -- Cheers, √

@sleipnir Second option, definitely for me. Also, we can either expose a materializer via the CommandContext, or recommend to use the SystemMaterializer. Thoughts?

@marcellanz @ralphlaude I think we could support both the java.util.concurrent.Flow-types AND Akka Streams—since there is no API in java to transform streams. OTOH, it is of questionable value to have...

@marcellanz Yes, the format should be opaque to the proxy, but of course this has implications over time for maintenance, interoperability if one wants to rewrite a function from one...

@kwehden Agreed—I'm a big fan of Postgres as an RDBMS

@sleipnir Even if it is delegated to infra, there'd still have to be a way to propagate it?

@sleipnir Sounds like a great request. One could look at the response type and the accept-header to negotiate the feature on/off.

@sleipnir Very WIP and untested, but have a look at https://github.com/cloudstateio/cloudstate/pull/317/files! :)

Agreed. And we also need to rework the TCK so that the different language-supports can run them as a part of *their* build—ideally spitting out a summary of all the...

@sleipnir @pvlugter Given how the TCK works I think it should be rather straightforward to create a Docker image for it and have the user run it against that Docker...