Today, I just feel to talk about some experiences on the thing called “thestreamwast”.
First I saw someone said online that streameast has some issues about security. And also it mentioned unauthorized streams. It gets me thinking, what the hell is a stream? So I started my exploring journey.
I googled a while and found that the stream is just a sequence of bytes. Sounds easy, right? It provides means for reading and writing bytes to its given backing store. So, what’s the point of using it? I mean, why not just use the backing store directly? I was confused.
Then I did some more digging and saw a bunch of technical terms like “live streaming,” “Apache Kafka,” and “Twitch.” To be honest, I didn’t quite get all that at first. But it seems like live streaming is a big deal.
After a lot of reading, I think I got some basic ideas about how live streaming works. It starts with raw video data, and then the data is sent to the server, after that, it delivers to the client. Simple, huh? And there was something mentioned about “non-blocking operations” that allow data processing without making the main thread stuck. I think that’s pretty cool.
Here are the main steps I tried:
- Search for the definition of “stream”: Find out it’s a sequence of bytes and can be used for reading and writing.
- Investigate the purpose of using streams: Still a bit confused about why not interact with the backing store directly, but moving on.
- Explore live streaming: Figure out the basic process from raw data to the client, and learn about non-blocking operations.
My conclusion
After a while, I finally get a whole picture of this thing. Streams can be used for filtering, collecting, printing, and converting from one data structure to another. You see, it is not that complicated. I think I’ll try to explore more about Apache Kafka and Twitch later. Maybe there will be something more interesting.
I hope this post can be helpful for those who are also interested in this kind of stuff. It is not difficult as you think.
