The Leo community was introduced to the new Labs, the UI that will serve as the alpha testing site. This is going to remain live and open to the community while updates are made to the production UI.
One of the big changes right now is the testing of LeoCache. This is infrastructure that is crucial going forward. It is also something that is going to completely change Hive.
Scaling is a crucial feature for any network. With blockchain, there is a problem with this. On Hive, we are more advanced than most other chains. However, there are still delays.
LeoCache was designed to address this problem.
So let us look at what is taking place and what it really means.
No Delays
During the Leo AMA, there was a threadcast that was record setting. During the show, there were like 400 comments made. After the show went off air, another 1,000 comments were added.
Why is this important?
It reverts back to the idea of scaling.
What was proven during the test was that the thread loaded as quickly with 1,400 comments as it did with 10. We have no idea what the upper limint is but we are off to a good start.
To contrast, have you ever noticed that when a blog post has a lot of comments, the page loading slows down? Many of the comments are not visible since the applications limit the cache by not loading them upon opening of the page.
This would be fatal for a project like threads.
We have to keep in mind that all of threads are comments. Even top line threads are actually at the comment level. There is a blog post created that serves as a container.
This is why LeoCache is crucial.
Rolling Out To All Of Hive
One of the discussions regarding the proposal submitted to the DHF was the fact that Leo is creating infrastructure that other applications can use. LeoInfra is a part of this which includes LeoCache.
In short, any application could tie into it and enjoy the benefits.
Will others adopt it?
That is anyone's guess. The thing is that Leo is not going to be on an island by itself. Whatever the outcome, the infrastructure is going to enhance this platform in ways that will allow for scaling. That means one application on Hive, at a minimum, is able to handle large numbers of comments.
Where this could have the most impact is upon threads itself. What happens if we are doing 100K threads in a day? 500K? Or a million?
Keep in mind the latest numbers that were out of Twitter was 500 million Tweets per day. Even at 1 million, we are talking about a drop in the bucket.
logo by @st8z