Decisions
Choosing well is a different skill from knowing a lot. Each page here takes a real fork, commits to an answer, and says plainly what that answer costs.
Anyone can list trade-offs and refuse to conclude. These pages conclude, which is the part that can be wrong, which is the part worth reading.
I rebuilt this site in Astro rather than Next, and the reasoning is a fair test of the decision, because you are reading the result and can check every claim in it.
Replacing cron with a queue is treated as an obvious modernisation. It is a trade, and there are systems where cron is the correct answer and the queue is a liability.
WebSockets are the default answer to the word realtime, and most realtime requirements are one directional. The server has something to say, the browser needs to hear it, and nothing goes back the other way.
This choice gets argued on flexibility and schemas, and both sides are usually arguing about the wrong thing. The question that actually decides it is whether anything in your system has to add up.
For problems rather than forks, see solutions .