Hi all,
I am just trying out akka-http and haven't been able to find much
information about how backpressure works when we use futures and run
operations async.
For example, if I create a REST API with a route that looks like this:
```
val route =
(path("users") & post & entity(as[NewUser])) { user =>
complete(createNewUser(user))
}
```
where the method `createNewUser(user)` spawns an async operation which
interacts with a database and returns a Future[User].
Say the database slows down and there is a backlog of pending requests,
does akka-http recognize that the futures are taking a long time to
complete, and then slow down the number of calls to createNewUser?
Also how does the execution context used to execute the futures affect the
backpressure? For example, if my database operations take place on an
execution context which only supports 4 concurrent operations, will
akka-http ensure that there are at most 4 pending futures/calls to
createNewUser at any time?
Thanks for any insights on this!
Josh
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
