Database Design for Web based RSS Feed Agreegator

Ok, if you're using mvc then you're definitely doing this a bit wrong... Consider mvc, its the model => view => controller framework. The whole point of the framework is to ensure a nice and clean separation of concerns.

When you start storing templates in your db, your muddling those concerns. What I would do is convert each of my templates into a partial view. The whole reason partial views exist is to serve as little code templates.

I would store the data only in the database.

So your app basically has this:

the db containing only the data required for a status update. a controller that loads this data, and then passes it to the relevant view a view that displays the data in its own required format.

So, reading this, I see the following specs:

1. I want to track popularity of blogs. This is accomplished by comparing their aggregate "likes" or whatever (retweets, etc) over a 48 hour period to their "normal" level.

2. I want to update my current count of likes, retweets, on a configurable periodic interval.

3. I need to be able to compute the effect of likes, retweets, etc independent of each other.

Seems the simplest way would be to use your third schema. It still allows you to collect all stats simultaneously or independently. The only effect would be if independent, there will always be some window of time where your current rankings doesn't reflect the true ranking while if simultaneous, your rankings just lag the "truth" by at most the update rate.

Anyway, then, you can periodically run a query for each post_id, compute the fb likes metric over the previous 48 hours + tweets metric over the previous 48 hours, etc, and use that to update your ranking.