development of a highly concurrent web service.
Imagine I want to build a web service(most probably a rest service) were it
is supposed to process many concurrent requests. The thing is that for
every request that arrives at the web service, some has to be processed
sequentially and some can be processed in parallel. How should I go about
doing so? Should the web service have some kind of go routine entrance that
depending on the call, it will send it to another GO routine responsible
for processing those requests and dynamically instantiate a GO routine for
every request that can be handled in parallel and send the request to it?
I want the client code to be blocking so that the client don't care how the
request is being handled and the just get a response on
their synchronous call. How will I make the web service not to return to
the client until the associated go routine is done handling the request?
Is this how you will build such web service? How else will you build
a Highly Concurrent Web Service With Go?
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.