squbs
squbs copied to clipboard
paypal
Akka Streams & Akka HTTP for Large-Scale Production Deployments
Having a JMX bean (or a field in an existing one) that show how many times a client is materialized? This may give us a quick debugging idea to see...
The squbs-testkit supports for `RouteDefinition`. We need to make sure it can support `FlowDefinition`, too.
For a `MergeHub` with `FlowDefinition` scenario, we would like to get the `Sink` as a response from an `Actor`, but with `ActorLookup`. However, `ActorRegistry` is not initialized at that point...
For a `MergeHub` use case, we need to retrieve the `Sink` with an`ask` to an actor. However, this requires us to block in `FlowDefinition`. Even though this blocking just during...
With Akka 2.5, `Agent` is deprecated. Please see http://doc.akka.io/docs/akka/current/scala/project/migration-guide-2.4.x-2.5.x.html#agents. It is being used in `squbs-unicomplex` for keeping state. We need to refactor it.
Currently, `Cubesupervisor` has a hardcoded `supervisorStrategy`. Please see https://github.com/paypal/squbs/blob/RELEASE-0.9.0/squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala#L593. We should make it configurable and each cube should be able to define its own supervisor strategy.
As a follow up to https://github.com/paypal/squbs/issues/487 and comments at https://github.com/paypal/squbs/pull/488, we should consider making some parameters `implicit` for Scala API.
There are scenarios where the pipeline for ClientFlow may need to be programmatically controlled. We need to make pipeline configuration overridable with programmatic parameters as any other settings passed into...
Thanks for your pull request. Please review the following guidelines. - [ ] Title includes issue id. - [ ] Description of the change added. - [ ] Commits are...
