Level 75
If you are really that concerned check out laravel vapor.
Dec 2, 2019
6
Level 2
Scalability on demand?
I've been through multiple tutorials, where the scalability basically begins since the application is first deployed by configuring load balancers and some guides go as far as making a separate server for each individual function (database, redis, application, etc) which is excessive cost wise honestly.
What if I configure a DO server that is simply enough for a year or two, I have everything there, my application, database, Laravel websockets and then when the time comes I need to assign more resources, how do I proceed in that case? would I need to start from zero to decouple my sever into multiple instances each one doing something different or is there a more simpler approach? what if I just need to allocate more storage? are there any good tutorials explaining these situations?
Any help is really appreciated.
Level 2
Uhh, my app is off the mark by 1 version (5.8) and why would I need to switch to Vapor when I can achieve the same with Forge, right?
Level 2
Anyone have a possible answer? I honestly refuse to believe that the only way is setting the load balancers and such from minute 0 because that would be a good waste of money. I of course gave a look to vapor, but it requires laravel 6+ and it costs triple the Most basic plan on forge and double the one that allows multiple sites. Remember I'm making these questions with saving money in mind.
Thanks in advance
Level 75
D.O. should have a guide on scaling up, and how to handle it.
Level 8
Have you looked into bref for serverless PHP. Then you could pick your cloud provider (e.g. Amazon AWS). I have not used it myself, but think it is quite popular.
Level 75
I don't use digitalocean, but I did a search and then around two seconds I found this article
But there were other results.
So let Google help you in cases like this.
Please or to participate in this conversation.