squbs
squbs copied to clipboard
paypal
Akka Streams & Akka HTTP for Large-Scale Production Deployments
Please see the commit https://github.com/anilgursel/squbs/commit/5596d8c10b0c42f88b09ff9de3093db977e84c44. It requires some updates and additions. However, some clarification is needed. Please see my comments at https://github.com/akka/akka/issues/21753.
The metrics collection and monitoring capabilities squbs provides should be discussed on a dedicated document instead of being spread around. This should also make it easier for operations folks.
We need to make it more clear in pipeline documentation that app config vs default config should be made more clear. Also, we need to talk about pre-flow and post-flow...
The current timer precision in TimeoutBidi is 10ms (at best).
Currently, the `Retry` stage takes `(T, C)` in and `(Try[U], C)` out. In some cases, the input is already derived from the context C and the output is attached to...
https://github.com/paypal/squbs/blob/82ef1b1b6bf1f91cb64ba589554f22505a91a4d6/squbs-pipeline/src/main/scala/org/squbs/pipeline/RequestContext.scala#L48 This cast can fail. It is worrisome because a client would normally expect the Failure to be some kind of HTTP thing. AFAIK, AKKA only has the Scala implementation...
Some scenarios are still not covered from pr 647 https://github.com/paypal/squbs/pull/647 Line 275: Line 255: Line 269: