Viewing a response to: @steemitblog/exploring-steem-scalability
Hi, My experience has taught me that any design that depends on a fully memory based solution is asking for a lot of trouble. From what you have described, it looks like the full nodes are setup to make this assumption. Why not use Redis instead? My experience with Redis has been very good and yet is is better when backed up by SSD but not mandated. this way a linear dropoff is avoided. One of the disadvantages of a dispersed cluster solution is that individual node performance becomes paramount. if enough of the nodes are slow then you have other security problems to worry about. using Redis seems like a good compromise and it will keep your code simple. regards Adarsh
author | adarshh |
---|---|
permlink | re-steemitblog-exploring-steem-scalability-20180413t074706602z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-04-13 07:47:06 |
last_update | 2018-04-13 07:47:06 |
depth | 1 |
children | 0 |
last_payout | 2018-04-20 07:47:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 679 |
author_reputation | 1,909,676,117,380 |
root_title | "Exploring Steem Scalability" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 49,812,474 |
net_rshares | 0 |