Should I use FastFuture with Akka Http

Akka Http uses FastFuture internally to avoid context switching
A common pattern is to make calls like

Unmarshal(decodedResponse.entity).to[Res]
   .map(..do domething)
  .recover(..do domething)

The map is usually very simple (transforming one case class to another, logging, etc.). Does it make sense to use fast future in these type of calls (again, assuming we are very confident the transformations are non-blocking )

Unmarshal(decodedResponse.entity).to[Res].fast
   .map(..do domething)
  .recover(..do domething)

Hi @eugenemiretsky,

there’s no downside to using it. There will only be an effect if the future you use it on is already completed. In that case, the operations will also be executed immediately.

Johannes