It depends largely on what you want/need to do with the just inserted information and if it's important to have it there directly on spot. CQRS doesn't promise you that but it promises that somewhere in the, near, future the data will be there. If it's just
for storing points or something then you're good to go. If your client applications rely on the one second time frame then it's likely better to opt for something else.
Grz, Kris.
Read my blog | Twitter Interested in Azure, ASP.NET (MVC), jQuery, WCF, EF, MS SQL, ...
Keep the forums clean: report to the moderation team!
XIII
All-Star
182789 Points
23485 Posts
ASPInsiders
Moderator
MVP
Re: Connecting every 1 second to DB
Apr 30, 2012 06:12 PM|LINK
It depends largely on what you want/need to do with the just inserted information and if it's important to have it there directly on spot. CQRS doesn't promise you that but it promises that somewhere in the, near, future the data will be there. If it's just for storing points or something then you're good to go. If your client applications rely on the one second time frame then it's likely better to opt for something else.
Grz, Kris.
Interested in Azure, ASP.NET (MVC), jQuery, WCF, EF, MS SQL, ...
Keep the forums clean: report to the moderation team!