I have trouble actually watching this screen cast, I’ll I get is sound and grey block. I have tried in 3 browsers, Opera, FF, IE8 and same result. Same is true if I download it and try to watch it in WM.
Is there an issue with the video?
Excellent screen cast. Not too bad writing code on the fly and getting it write the first time – well done!
Was starting to write my own CQRS infrastructure but after watching this I am now thinking that NCQRS will save me a heap of time. Lets see how it goes.
How would you go about lets say using MSMQ or NService bus for commands and for events ?
And would you use NService or MSMQ for the command handlers (maybe in place of WCF)? or would you only use MSMQ or NService bus for the event handlers ?
I’m a little lost when it comes to needing to scale out, I can see that by using DI it is very easy but unsure where you would start scaling (events or commands or both).
And lets say you scale out event handlers and not command hanlders, is this why you should only ever change state of an AR within an command handler and never in an event handler?
Very nice screencast, I quite enjoyed it. I do have a question, in regards to the denormalizers updating the read models.
What about concurrency? The read model for listing tweets is not an issue, but if you end up with more than one event closely timed that are going to try and update the user’s tweet count read model, how do you avoid concurrency errors or runtime errors around the update?
Is there a way to reconcile the read model based on events? Say for example, you add the read table for the tweets per user after some tweets were created.. i don’t see an easy to way to go back and update that data.
I have trouble actually watching this screen cast, I’ll I get is sound and grey block. I have tried in 3 browsers, Opera, FF, IE8 and same result. Same is true if I download it and try to watch it in WM.
Is there an issue with the video?
great screen cast -going to take a look at the rest of your site
Excellent screen cast. Not too bad writing code on the fly and getting it write the first time – well done!
Was starting to write my own CQRS infrastructure but after watching this I am now thinking that NCQRS will save me a heap of time. Lets see how it goes.
Cheers
Great screencast, helped me a lot.
Great screencast! Thank you. I’m starting today with a Ncqrs project in production.
How would you go about lets say using MSMQ or NService bus for commands and for events ?
And would you use NService or MSMQ for the command handlers (maybe in place of WCF)? or would you only use MSMQ or NService bus for the event handlers ?
I’m a little lost when it comes to needing to scale out, I can see that by using DI it is very easy but unsure where you would start scaling (events or commands or both).
And lets say you scale out event handlers and not command hanlders, is this why you should only ever change state of an AR within an command handler and never in an event handler?
Very nice screencast, I quite enjoyed it. I do have a question, in regards to the denormalizers updating the read models.
What about concurrency? The read model for listing tweets is not an issue, but if you end up with more than one event closely timed that are going to try and update the user’s tweet count read model, how do you avoid concurrency errors or runtime errors around the update?
Thanks.
Remi.
Great job! I really appreciate your efforts of creating this
Is there a way to reconcile the read model based on events? Say for example, you add the read table for the tweets per user after some tweets were created.. i don’t see an easy to way to go back and update that data.