field: backend / queues / data boundaries
Load rarely starts with abstract architecture. First you need to understand real scenarios, data boundaries, background jobs and places where a simple synchronous model stops being honest.
Only then do queues, read models, event-driven loops and separate services appear. Otherwise architecture becomes expensive decoration.