Hi... Your 5-minute video was insane. I was looking for all the explanations in the video for so long. I had to see with my own eyes what that "block" means and I clearly understood. Thank you sooo much!
I'm replying to you because you are one of the more recent comments on this. I still don't get what he is saying about the storage. Let's say you have a LAN and you have a SAN. Obviously we can have a file server with locally attached disks and we have a file storage on that. But, if we have a SAN then it could use either block or presumably object storage... why would one be better over the other? The files stored are going to be the same. Even if we said it's in the cloud, why use one over the other? What does Block do differently that object doesn't and vise versa. He put stuff like audio in the object storage right but really audio can go into block as well. So why not? This is the part I don't get. He makes it, and everyone else as well makes it seem like block is only for databases because of the statement that there is a database that stores the location of the files within the storage?!?!? Is it just that object storage is different because you only need to know the ID and nothing else matters? So if you wanted to have say a music application and someone wanted to play a song, you just have something that says Nirvana - "Smells Like Teen Spirit" = ID:154354838-d654e651f-es354fe so no matter where it is really stored you only need to feed that ID into the application and the storage does the rest? Like to an end user, each looks the same. You still have to know where: Bucket (possibly) and then the location after that to find a file as opposed to server/folder/folder so I am just not quite understanding.
sorry for the confusion and admire your observation. I think I did not make it clear about the first one (file storage). The user should get one box, where the emphasis is on the full path + file name. The second one (block) should get four boxes because the user gets the whole data (four boxes). The object storage should emphasize ID and metadata (decription of the data). Thanks a lot for pointing out the confusing part. Many thanks.
@@ShuxiangSun123 Thank you for letting me know the intentions. Makes sense now. I’m old in the game so I really want to wrap my head around when and why to use specifically object storage. I like your videos and watch many of them. Thank you for sharing. Do you have an online class / course to attend?
I always get confused by block storage because that's how filesystems store files anyways. They're broken into blocks and those blocks can be stored anywhere in the filesystem
Hi sir, your videos or amazing such a clear content. Thanks for providing such good knowledge to us. Sir please do videos on Docsis technology and wifi and wifi4all concepts.
@Sunny Classroom But I have a question for you with regards to the animation starting at 4:10. In my understanding, blocks are small fragments of data that are, if put together, could compose a file that is typically stored in a tile storage, no? And if so, the illustrated representation of blocks should be smaller objects inside each box, no?
Good question, but what you are referring to as "blocks" is actually called sectors on a spinning drive, and block storage is different. These are the concepts of Enterprise-class storage that Sunny is making easy to understand by giving examples. Please check for how hard drives work. Here is a link to a video that explains very nicely; hope it helps.th-cam.com/video/wtdnatmVdIg/w-d-xo.html
So... I still don't understand really the difference and I would really like to see the difference in actual use. For example, you say that block storage is for structured use however it is used in SANs and NASs right... so why show different data in block storage vs. object storage when it could be the same? The same goes for file storage. What does, for example an MP3 file look like in each? Why is it better suited for each vs. not the other? I guess that's my question also. To the end user it is going to pretty much look the same right? So you are essentially referring to applications that work with the data is easier to use object storage vs block? IDK... I understand what you are saying I just don't understand what you are saying. Like I can regurgitate what you said back to someone who asks me but I have no idea what I am saying.
Thank you for the contents. I have a question about how to define my laptop's Hard Drive. I can install database and any other applications, I can store files and hierarchical structure (Folders and sub-folders), I can also store objects like movie clips... Is the storage in our personal PC everything or its one thing?
Yes, your computer also has storage, and it's local. When you are dealing with laptops or desktops, they will mostly have one or two drives, and they are local to the system. But here, Sunny is explaining the server or enterprise-class storage, which is used in Data Centers. What you are referring to is applications or contents, and Sunny is explaining the concept. If you still have questions, please invest some time in the CompTIA Server+ topic "Server Hardware Installation and Management". Good Luck.
![ไปอยู่ไสมา - ช๊อปเปอร์ โตเกียวมิวสิค [ OFFICIAL MUSIC VIDEO ]](http://i.ytimg.com/vi/sWuVNbRTJbc/mqdefault.jpg)
Had never seen a simpler, yet thorough explanation of storage types !! This channel deserves a million subscriptions.
i AM Spanish native, I loved this explanation since I'm not very technical. thanks a lot for the mini videos to explain.
Hi... Your 5-minute video was insane.
I was looking for all the explanations in the video for so long. I had to see with my own eyes what that "block" means and I clearly understood. Thank you sooo much!
finally good content from a man who understands a concept and can relay a point efficiently. bravo sir youre one in a million
I'm replying to you because you are one of the more recent comments on this. I still don't get what he is saying about the storage. Let's say you have a LAN and you have a SAN. Obviously we can have a file server with locally attached disks and we have a file storage on that. But, if we have a SAN then it could use either block or presumably object storage... why would one be better over the other? The files stored are going to be the same. Even if we said it's in the cloud, why use one over the other? What does Block do differently that object doesn't and vise versa. He put stuff like audio in the object storage right but really audio can go into block as well. So why not? This is the part I don't get. He makes it, and everyone else as well makes it seem like block is only for databases because of the statement that there is a database that stores the location of the files within the storage?!?!?
Is it just that object storage is different because you only need to know the ID and nothing else matters? So if you wanted to have say a music application and someone wanted to play a song, you just have something that says Nirvana - "Smells Like Teen Spirit" = ID:154354838-d654e651f-es354fe so no matter where it is really stored you only need to feed that ID into the application and the storage does the rest?
Like to an end user, each looks the same. You still have to know where: Bucket (possibly) and then the location after that to find a file as opposed to server/folder/folder so I am just not quite understanding.
Actually, i consider this amazing video is one of the best videos that explained it.
i watched other explanations on block vs file vs object but I stopped here. great explanation. thank you sunny.
Funny animations at the end. Not sure I understand why the last person only fetches one piece but the other ones fetches four.
sorry for the confusion and admire your observation. I think I did not make it clear about the first one (file storage). The user should get one box, where the emphasis is on the full path + file name. The second one (block) should get four boxes because the user gets the whole data (four boxes). The object storage should emphasize ID and metadata (decription of the data). Thanks a lot for pointing out the confusing part. Many thanks.
@@ShuxiangSun123 Thank you for letting me know the intentions. Makes sense now. I’m old in the game so I really want to wrap my head around when and why to use specifically object storage.
I like your videos and watch many of them. Thank you for sharing. Do you have an online class / course to attend?
Fantastic Demonstration! Just unique one your all content. Thank you sir
Thanks for the clear and concise explanation.
Another great lesson. Thank you for the effort you put into creating your content. I enjoy watching your channel!
Subscribed. Well done.
I always get confused by block storage because that's how filesystems store files anyways. They're broken into blocks and those blocks can be stored anywhere in the filesystem
Easy understand thanks
thank you, love the content. I did see the graphic says "matadata" but the bullet points does say "metadata".
Aa usual so wonderful!
Hi sir, your videos or amazing such a clear content. Thanks for providing such good knowledge to us.
Sir please do videos on Docsis technology and wifi and wifi4all concepts.
very good explanation! Thank you👍
wow, this makes sooo much more sense. thanks
Wonderful Video , thank You !!
Thank you 😊
Fantastic lesson.
Good
Well done. Had to like and subscribe. Thanks!
Thanks you
Sunny, can you please do a video on subnetting class A? Your videos are so helpful, but i am having a very hard time with class A.
thanks
@Sunny Classroom
But I have a question for you with regards to the animation starting at 4:10.
In my understanding, blocks are small fragments of data that are, if put together, could compose a file that is typically stored in a tile storage, no? And if so, the illustrated representation of blocks should be smaller objects inside each box, no?
Good question, but what you are referring to as "blocks" is actually called sectors on a spinning drive, and block storage is different. These are the concepts of Enterprise-class storage that Sunny is making easy to understand by giving examples. Please check for how hard drives work. Here is a link to a video that explains very nicely; hope it helps.th-cam.com/video/wtdnatmVdIg/w-d-xo.html
thank'u
THANK YOU!
Thank you
🎉🎉
So... I still don't understand really the difference and I would really like to see the difference in actual use. For example, you say that block storage is for structured use however it is used in SANs and NASs right... so why show different data in block storage vs. object storage when it could be the same? The same goes for file storage.
What does, for example an MP3 file look like in each? Why is it better suited for each vs. not the other? I guess that's my question also. To the end user it is going to pretty much look the same right? So you are essentially referring to applications that work with the data is easier to use object storage vs block? IDK... I understand what you are saying I just don't understand what you are saying. Like I can regurgitate what you said back to someone who asks me but I have no idea what I am saying.
Thank you for the contents. I have a question about how to define my laptop's Hard Drive. I can install database and any other applications, I can store files and hierarchical structure (Folders and sub-folders), I can also store objects like movie clips... Is the storage in our personal PC everything or its one thing?
Yes, your computer also has storage, and it's local. When you are dealing with laptops or desktops, they will mostly have one or two drives, and they are local to the system. But here, Sunny is explaining the server or enterprise-class storage, which is used in Data Centers. What you are referring to is applications or contents, and Sunny is explaining the concept. If you still have questions, please invest some time in the CompTIA Server+ topic "Server Hardware Installation and Management". Good Luck.
Hey, how can i contact you if im interested in Ads/Affiliate