online-bridge-hackathon / DDS

An api that returns DDS results for a given deal or partial deal
https://bit.ly/bridge-hackathon
Apache License 2.0
4 stars 6 forks source link

Add AppEngine app. #69

Open tameware opened 4 years ago

tameware commented 4 years ago

Either just front end or start with api.py and add in the front end afterward.

What are the advantages and disadvantages of deploying the back end to AppEngine as oppose to a Compute Cluster?

Will deploying to AppEngine be more straightforward that deploying to a Compute Cluster?

suokko commented 4 years ago

I was thinking a couple of days ago if App Engine would be right server side solution. I found following limitation for App Engine.

Application code only runs in response to a web request, a queued task, or a scheduled task, and must return response data within 60 seconds in any case. A request handler cannot spawn a sub-process or execute code after the response has been sent.

This is a deal breaker for DDS service. DDS service should be collecting multiple request together to allow libdds better utilize Translation Table. Average solving time improves between factors of 2 and 10 if we improve translation table utilization.

Other components could run efficiently on App Engine.

Source: https://stackoverflow.com/questions/15801735/does-google-app-engine-support-c