No need to be condescending. ES and ED architectures have good use-cases. And CRUD has good use-cases, and RDMSes and time series and document databases. Non w

No need to be condescending. ES and ED architectures have good use-cases. And CRUD has good use-cases, and RDMSes and time series and document databases. Non will ever fit perfectly and non are a silver bullet. Choosing the right architecture is an an art. Experience helps. And being able to look into the future even more. Point being: a silly parameter as "wether you need the response to a request to have the data" is certainly not the only metric to base architectural choices on. It's not even a significant metric. It's at most a technical requirements. And one that can be fulfilled with many architectures. Like event sourced architectures even.