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

[dan-da]

> was modified to include the fancy new charts and got worse over time as the API got more and more popular.

haha.  yes, I specifically recommended against these changes, especially [enabling the CORS header](https://github.com/bisq-network/bisq-markets/issues/14#issuecomment-430691746) due to traffic/scaling concerns.  Doing things this way meant that every end-user browser would be calling the APIs directly multiple times per page request and could do so from 3rd party sites.  Also, afaics, the fancy new chart is less fancy, shows less information, and is generally worse than the prev chart.  but whatever.  anyway, I left the project in part because these changes were being forced against my recommendation.

Still though, I doubt that that the APIs are yet regularly being called at 1000+ reqs/sec.  That's pretty huge traffic.

So @wiz have you checked if opcache extension is enabled on the server yet?

> Perhaps some newly added queries for the charts weren't being cached properly

There were no newly added queries.  With the exception of the CORS header, the new page design and charts was purely frontend work done in a separate repo.







-- 
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-552509919
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191111/af823619/attachment.html>