Yeah, pretty much the same thing. Gathers up analytics data and dumps it in a queue (request, referer, page being looked at, other shit like that).
And the long-running thread is the queue?
I have two suggestions for you:
If the server isn't virtual, write a Windows Service that looks at the web server logs and inserts data from that. (Make your web server super super simple.) This works with a physical server or a cloud machine that pretends to be a physical server, but not as well from something like a Azure Web Application, since the "web log" is a big cloud blob and it's hard to do random seeks into a big cloud blob.
Move the entire queue into a Service, and use some simple IPC to get your data there.
The question is now, what is the recommended way of doing interprocess communication between the website and the service?
I'd probably just use TCP/IP to localhost over a known port. More than that's probably overkill. You'd still have to serialize the data though.