We are trying to write some tests to prove following statements about 
reactive servers

1. Thread context switching has cost associated with it.  So creating lots 
of threads is problematic.
2. With tens of thousands connections per server, reactive servers utilise 
the server resources more effectively. 

We have seen these situations in production on one or more projects, but 
there is no code with tests which we can point people to and say 'run and 
see yourself'.

There are few examples discussed in the book 'Reactive Programming with 
RxJava' with sample code available at 

I was curious to know if there are already some samples which demonstrate 
the effects of thread context switching in blocking servers and how akka 
http's reactive architecture scales better. (in terms of resource 
utilisation and stability)


** New discussion forum: https://discuss.akka.io/ replacing akka-user 
google-group soon.
** This group will soon be put into read-only mode, and replaced by 
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
>>>>>>>>>>      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.

Reply via email to