ZipStream-PHP VS laravel-backup

For downloading I tried this https://github.com/maennchen/ZipStream-PHP and later tried this as well https://github.com/stechstudio/laravel-zipstream but the download "hangs" until all photos are processed (until the loop is done) and only at the end it shows the save dialog. Then when you save it, it's already downloaded, because it downloaded it during that "hang" period. The problem is it looks like a "delay" when user clicks download button. When working with small amount of data that's tolerant, but when I want to download, for example, a few GB, it still downloads it but it's doing it in the background. When I open network tab I see the request is pending and the size column is growing (cause it's downloading files) and then after couple of minutes (it depends on your download speed) it shows a save dialog.

https://github.com/jeremykenedy/laravel-logger#authentication-middleware-usage https://github.com/beyondcode/laravel-dump-server https://github.com/barryvdh/laravel-debugbar https://github.com/laravel-shift/blueprint https://github.com/spatie/laravel-backup https://github.com/spatie/laravel-permission https://github.com/spatie/laravel-activitylog https://github.com/realrashid/sweet-alert https://github.com/rappasoft/laravel-livewire-tables https://github.com/yajra/laravel-datatables https://github.com/Labs64/laravel-boilerplate https://github.com/creativetimofficial/argon-dashboard-laravel https://github.com/the-control-group/voyager https://github.com/beyondcode/laravel-er-diagram-generator

8. spatie/laravel-backup

4. spatie/laravel-backup https://github.com/spatie/laravel-backup

In my case I'm dumping + zipping the entire database at the application level. In my case is as simple as adding a library [1], scheduling the job and transferring to AWS S3 (my main application is on DigitalOcean)

[1] https://github.com/spatie/laravel-backup

Database backups via php artisan backup:run