It’s kind of a tacit art more than science. It also depends on the motivations of the architect and the team. Ceteris paribus (i.e. we do not consider application design here), I’ll say there’s the ideal, and there’s the pragmatic. Ideally, the queue-based load leveling pattern calls for a high throughput queue to be placed before services (such as that for data persistency) as it may be slower (memory vs disk, etc....

In the past, I used to write long form blogs, with proper sentences and paragraphs :) Restarting my site this 2020, I think it may not be effective anymore: Slow to write: which means I write less, not a bad thing, but I want to record more, for memory. Slow to read: I don’t think most readers have time / patience to read long form by someone like me, I am not Paul Graham, not that he write too long too....