Usually you update with Composer locally and on the server.

But with FTP you just transfer the "app"-folder.

If you don't have SSH access to your server then you must upload all the files :-(

What if I ave multiple servers... Do I need to update composer first on each servers and then upload files online...

Does not look like laravel is made for big projects having high traffic.

Just don't use FTP, but use Git instead. On you local development server, run composer update if you need to. Commit the composer.lock file and on your development server, pull the changes in via Git and then run composer install so you're up-to-date with the lock file.

If you need fast/simultaneous deploys you could look into symlinking, like Rocketeer does (https://github.com/Anahkiasen/rocketeer) That first clones the repo in a new release dir, run composer install and when successful, replace the symlink from the old to new dir. So you can switch directly back if you need to.

FTP is very outdated/slow and you shouldn't use that.

Thanks.. I will check rocketeer.. will check how can i deploy new changes on multiple servers..