BACKGROUND

So I'm working on a project that is all about tracking user activity on a site:

1. How much time spent on site
2. how many activities a user has started, finished,
3. How many times a user has come to the site
4. etc.

And of course they want lots of reporting on all these aspects.

The site gets a fair amount of traffic and I can see all this logging
creating quite a bit of traffic especially over years.

QUESTIONS

1. Not knowing much of anything about nosql implementations, would
this project be worth exploring  nosql?

2. If I stick with MySQL, are there some ways I can architect at the
get go that won't make it a bear to work with in say 3 years. (ie some
ginormous table). I was thinking either try and get some sort of
business process retention policy (ie we only need to worry about a
years worth of data) or database retention (ie dynamic tables that
store a years worth of data user_time_2012, user_time_2013 ).

Anyway would love to get some feedback on this.

Thanks, Mark


--
-----------------------------------------
Mark Steudel
P: [masked]
F: [masked]
[address removed]

. : Work : .
http://www.mindfu...

. : Play : .
http://www.steude...

. : LinkedIn : .
http://www.linked...