BackendHigh signal
CQRS
Also written as Command Query Responsibility Segregation
Splitting the code paths that change data from the ones that read it, so each can be designed and scaled for its own very different job.
Think of it like
A restaurant with separate doors for deliveries and diners: the same building, but the traffic has nothing in common.
Junior or senior?
Often over-applied.
Senior sounds like
Can explain why the complexity was warranted, and is comfortable saying most systems don't need it.
Ask them
“What made CQRS worth the extra complexity there, rather than a simpler design?”