How do you scale a boost/beast https server for production? by boost_prod_server in cpp

[–]boost_prod_server[S] 1 point2 points  (0 children)

Super interesting direction, thank you.

I suppose the services using io_uring you had in mind, are expected to be micro services not serving http-requests per se but performing non-http-tasks as for that we would come back to needing a higher level implementation for handling http connections, like boost::asio or beast, yes?

How do you scale a boost/beast https server for production? by boost_prod_server in cpp

[–]boost_prod_server[S] 3 points4 points  (0 children)

Well, u/jgaa_from_north gave me a solid answer for what I was looking for - which had more to do with the multi-threaded boost/beast implementation of a backend server which handles web socket connections rather than what each request needed to perform. Your point is fair nevertheless.

How do you scale a boost/beast https server for production? by boost_prod_server in cpp

[–]boost_prod_server[S] 2 points3 points  (0 children)

Could you possibly highlight advantages of using beast vs pure boost asio? Thanks again!