If you're developing a HTTP API (what most would call REST) how does that fit along side a Task-Based UI and CQRS? How can you create a REST API with CQRS? For starters, resources don't need to map to Entities. Second, HTTP Methods don't need to map to CRUD. Resources can be whatever you want them to be. In which case, they can be commands and queries.
🔔 Subscribe: [ Ссылка ]
💥 Join this channel to get access to source code & demos!
[ Ссылка ]
🔥 Don't have the JOIN button? Support me on Patreon!
[ Ссылка ]
📝 Blog: [ Ссылка ]
👋 Twitter: [ Ссылка ]
✨ LinkedIn: [ Ссылка ]
0:00 Intro
0:43 Entities & CRUD
3:35 Resources
8:12 Sample Application
#cqrs #softwarearchitecture #api
Is a REST API with CQRS Possible?
Теги
REST API with CQRSsoftware architecturesoftware designcqrsevent sourcingdesign patternssoftware architectasp.netsoamicroservicesevent driven architectureazure service busdistributed transactionsmessage queuemessage queuingmessaging patternsservice oriented architecturemicroservice architecturedomain-driven designrest api iwth cqrsrestrest apirestful web servicesrest webservicehttp api.net.net coreAsp.net core
