I have an very quick/lightweight mvc action, that is requested very often and I need to maintain minimal response time under heavy load.
What i need to do, is from time to time depending on conditions to insert small amount of data to sql server (log unique id for statistics, for ~1-5% of queries).
I don’t need inserted data for response and if I loose some of it because application restart or smth, I’ll survive.
I imagine that I could queue somehow inserting and do it in background, may be even do some kind of buffering – like wait till queue collects 100 of inserts and then make them in one pass.
I’m pretty sure, that somebody must have done/seen such implementation before, there’s no need to reinvent wheel, so if somebody could point to right direction, I would be thankful.
I agree with @Darin Dimitrov’s approach although I would add that you could simply use this task to write to the MSMQ on the machine. From there you could write a service that reads the queue and inserts the data into the database. That way you could throttle the service that reads data or even move the queue onto a different machine.
If you wanted to take this one step further you could use something like nServiceBus and a pub/sub model to write the events into the database.