[bisq-network/proposals] Decentralize the Bisq Markets API service (#165)

wiz notifications at github.com
Sat Jan 11 14:17:45 UTC 2020


> I will downvote the proposal if it attempts to decentralize and/or prematurely optimize via load balancing etc. The simple service should be written first

Well yes, the current code is written to run on a centralized instance of Google Appengine so it wouldn't be possible to decentralize it or run multiple nodes before making the new simple API service layer... Like I said we can work out the technical implementation details separately, this proposal is for the general goal of "decentralize all the things" along with the overall spirit of Bisq, so I think we are on the same page? Not sure why that would be controversial, as it's better and cheaper to do self-hosted.

> considerations can be made as to whether it needs further performance improvements like load balancing across multiple instances, whether it needs (and merits the resources and funding) to be decentralized right now, etc.

The purpose of decentralized self-hosted nodes isn't primarily for performance reasons (although that is an added benefit). The primary purpose of this proposal is to remove the centralized CPOF of having a single instance, and to move away from Google, thereby increasing the availability, privacy, and censorship resistance of the API service. There's no reason why we shouldn't do this, as it would save money over Google which is relatively expensive compared to cheap VMs we can rent anywhere.

-- 
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/proposals/issues/165#issuecomment-573320757
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200111/446258eb/attachment.html>


More information about the bisq-github mailing list