By the way, does this worker proposal going to cover maintenance of Bitshares.org or in separate worker proposal?
do you plan to report on usage stats?Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).
do you plan to report on usage stats?Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).
For the uptime stats, latency and availability will be used status pages as mentioned in worker. One for all listed Public API's and one separate for just nodes listed in this worker.
When you already mentioned, maybe it would be good to make an offer:
In case that this worker gets approved/voted it would be nice as respect and support of BBF infrastructure worker, that we can wrap our nodes under their balancers, and add their balancers/nodes to separate status page (their proposal is having milestone for development, we have it using uptimerobot), to get more data from monitoring to be compared, improve bug tracking, add more transparency to the stake-holders, etc.
Personally, I do believe that such co-operation would be of great benefit for everyone.
do you plan to report on usage stats?Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).
For the uptime stats, latency and availability will be used status pages as mentioned in worker. One for all listed Public API's and one separate for just nodes listed in this worker.
When you already mentioned, maybe it would be good to make an offer:
In case that this worker gets approved/voted it would be nice as respect and support of BBF infrastructure worker, that we can wrap our nodes under their balancers, and add their balancers/nodes to separate status page (their proposal is having milestone for development, we have it using uptimerobot), to get more data from monitoring to be compared, improve bug tracking, add more transparency to the stake-holders, etc.
Personally, I do believe that such co-operation would be of great benefit for everyone.
yeah, I'd like to know whether nodes are actually used (by users), to make sure none of us wastes time and money.
i like the idea of having more infrastructure with official worldwide nodes as proposed.
a few points to consider:
- there is no node in south america. i understand blockchain usage in general is not so popular here as other continents, still i think a node in Brazil or Argentina can bring some value.
- will you consider on hosting 1 elasticsearch node ? i think that if the wallet start using the feature we might need 1 more official node available(there is already 1 up from the BBF infrastructure worker rest is community members aka @clockwork).
price looks reasonable and APAsia already have a reputation in the community, i think it will go throw.
pd: also no node in Africa where the usage is probably even less than South America. Node in Hong Kong ?
_____________________
- I've personally tried to use best of my networking knowledge and create a pattern on the globe to utilize maximum availability. We did first (and only) public node in Australia and Canada, covered from East to West Coast of USA (where last year was only Xeldal and broken Texas node - before movement of witnesses re bitcrab vote and requirement) and all i'm saying we really had careful picks not just random purchases. I intend to keep utilizing network and optimizing its costs.
- I would point out that ES node that we would be hosting through worker has only sense having home in USA and best ISP for it would be Privex.io - Alex (Clockwork - Witness) is hosting ES in Asia and Fabian (Xeroc - BBF) is hosting ES in Europe.
Thanks for original input and feedback and hope to read more from you on this. Very important topic indeed, since we got into the problem with finance from scalability issues.
Just to clarify...Asia is my API node (seoul)...my ES node is in Finland.
Would be willing to relocate it if I find appropriate host in Asia (or anywhere) if needed.
voted
Excellent work so far.
Additional ES nodes (in US or China) would be great for the community. Will definately be voting for the replacement worker
+++