I think your better off building up a simple test case, using your assemblies and figure what you need as you go - (however, a design or plan to work to is much needed and worth the time spent on it) it all depends I guess on what kind of context your developing in. Are you on a timeframe, can you afford to experiment, if so then go for it, otherwise, while your waiting for an answer, I suggest you examine your brief or spec and break down exactly what your solution has to do, why, when and how etc...list the critical tasks and for each task, look at the implications or possible weaknesses you need to cover.

Caching is important, but I would imagine this is already well catered for in the web framework your using.

I always find its best to learn first hand, take advice sure, but always give it a good go first. This might seem like I am teaching you to suck eggs, I am not, but its the only advice I can give.

Look closely at your requirements first, following a pattern or example is fine, but your own design should be more important...then again I could be wrong!...

Your project looks fine, but if you get the opportunity, make a copy of it and run through a common process start to finish and see where you get to...when u hit a wall - shout.