4 ms·
Small note that the app in the post was not Rails, it’s a Golang app. You’re right in that PHP couldn’t fail like this though, as the isolation level is at a u
by lawrjone 3y ago
Small note that the app in the post was not Rails, it’s a Golang app.
You’re right in that PHP couldn’t fail like this though, as the isolation level is at a unix process, where the OS should contain all your errors.
- stefano_c 3y agoThe irony is that in a normal Rails app workloads are already split by default (requests and background jobs are handled by different processes that share the same codebase).
- lawrjone 3y agoYep, it's a very normal thing in the Rails world to separate things like this. For Django too. I'd encourage people to look a past just the splitting of workloads though. The other point about resource limits for shared resources across workload tiers is really key, such as having very granular database connection pools even inside of a single workload deployment. That's less common – though not unheard of – in Rails-land.