Uploading Large Files in ASP NET Core Web API - Performance Increase With Streams

Hi everyone. My name is Marinko Spasojevic and in this video, I will show you how to handle uploading large files in ASP.NET Core. I will talk about why using byte[] or MemoryStream can be problematic and discuss the benefits of using streams instead.

By leveraging streams, we can significantly improve the performance and scalability of our application when handling large files.

As usual, If you like the video please don’t forget to hit the like and subscribe buttons. It helps a channel a lot and supports my work here as well.

FOLLOW US ON SOCIAL MEDIA!

[CodeMaze]

Thank you all for watching and for your support.

[jacksonmwangi]

@CodeMaze, thank you very much for this video, it couldn't have come at a better time

[Mr.Pavel]

Thanks for the video, it's very nice solution! about a month or two ago I had to solve a similar problem and now I can compare both solutions :)

[PankajNikam]

Thanks for the video, use case of this can be like a video upload service like YouTube. Cool feature to add to this would be reporting real-time progress of the bytes uploaded to the consumer so that they can show a progress bar as to how much is remaining.

[harrisonwell]

If I need to retrieve a lot of images from the directory, Can I Cache them for faster retrieval?

[MisterKoko]

Thank you for the video!
In the slide you wrote "With byte[] or MemoryStream, the entire file is loaded into memory before processing" - but that's not the case for MemoryStream, that's a stream, isn't it?

[joysamuelkamlomo]

What about doing heavy complex calculations, data analysis stuff etc

[nicoxxxi]

What is happening with your site? I am receiving some errors

[davestorm]

I followed as much as I could, but getting
Unable to resolve service for type while attempting to activate
at type, Type requiredBy)