[bisq-network/bisq-markets] Re-implement Markets API service with pre-caching proxy + risq backend (#20)

[wiz]

> the webserver by itself shouldn't start failing until 100's of requests/sec

@dan-da Actually the API service does get hundreds of requests each second. I thank you for your PHP implementation and it served Bisq well over the years, but I think we are kinda outgrowing it and need something cloud based to handle the load, at least for the short term... We can look into self-hosted smart-caching solutions to move away from Google, but right now my primary goal is to return the service back to 100% uptime with reasonable performance and response times.

> I think it isn't a good idea to rush this now in the last hours of the proposal phase.

@ripcurlx Well to be honest, and with all due respect, we're not rushing this... if you look at the commit logs you'll see we've been continuously testing and working out all the bugs in this API re-implementation over the past few weeks. I just waited to create the PR until we were certain it was 100% ready for review.

Since @m52go ACK'd it and @ripcurlx didn't find any issues with the new API service (other than discrepancies where the old backend is missing things), I'm going to proceed with migrating the production markets.bisq.network service to Google Appengine using this PR. We will continuously monitor the service, and if there are issues found we will fix them right away.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-markets/pull/20#issuecomment-552681410
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191111/a527edef/attachment.html>