Naming of CRUD interface and best practices #1
Description
Hi, thanks for sharing the code.
Could you explain/give some recommendations about the CRUD interface? You called it QueryAllCustomersCRUD with suffix CRUD (create, read, update, delete) but "Query" indicates reading only at the same time.
- Would you add an UpdateCustomerCRUD for update operation or rename it to CustomerCRUD to contain all CRUD Operations (but even with that it would collide with the command approach)?
- Furthermore do you think having commands, queries and usecases would be a cleaner approach?
Maybe you have some experience with this architecture in a real project and can share some best practices?