Could you make separate videos about each of below topics explain it in details with real world examples. please ? - Separate Ready and Write ( Insert, update & delete ) connection to database. - Batch inserts & updates. - Don't synchronous reports ( but report in queue so other tasks in app won't slow because of slow reports ). Also what do you think of using Laravel Octane with Swoole or FrankenPHP for scaling ?
I have some videos on my backlog for those topics 🙏 I rarely use Octane, but the way I’d use it is to optimise specific routes. For example, I have a /pingback route that is used by client machines to signal their status once every minute. I run this route with Octane because it gets used 600-800 times per minute. Using Octane, we can skip setting up the entire framework that many times, and thus making the route much faster
Amazing tips as always, its the first time i hear about pre-computed json files in cdn, wonder how i can utilize it one day, Thank you and Best of luck!!
@@sabatino-dev I'd be curious about some insights on how you gained the first customers for your SaaS, maybe you could do a video about that in the future :)
Currently no plans of doing that unfortunately, but that may change in the future. You can join the discord server where I'll do announcements of this type of stuff discord.gg/CPnUMM7s
In many systems full-page cache applies to non-logged in users only, because of state as you pointed out. Alternatively, you could fetch state asynchronously using an API.
Why do you need to use AWS DBMS service when you have AWS Aurora or AWS RDS Multi-AZ? And regarding precomputed files and CDN, your solution involves some client side processing, the app is not full server side from what i understand, involving a JS framework/library or some vanilla JS is required, meaning that Laravel is not part of this improvement.
Initially we hosted our database at Linode (no read-replica), so we had to use DBMS to migrate off of Linode. Regarding the precomputed files -> Laravel is in fact part of the solution, it validates the data, merges open orders on it, invalidates caches, marks orders as stale, sends events, ... - the app is in fact a Vue SPA, but Laravel does a lot of processing behind the scenes.
Currently no plans of doing that unfortunately, but that may change in the future. You can join the discord server where I'll do announcements of this type of stuff discord.gg/CPnUMM7s
