If you're talking about Julie's EF in the Enterprise course, I've watched it three times to get it all. Not that it's complex. It's that there is ALOT in it.

At some point I'll need to look at MVVM, but right now, too much on my to-do list

>I like the MVVM pattern for a lot of reasons, but in regard to speed, I think that is probably a function of how the viewmodels are structured and the patterns used within them. Ultimately, whether you are using MVC or MVVM you are going to pull a subset of data from the backend and that is where the speed comes in. I'm leaning strong toward webservices from what little I know so far, so the calls will be a little different from the MVC addressing. Not sure what the tradeoffs are there. Again, I suppose that depends on how its designed and based on who is using what it seems either one could work very well ( if you were John Papa or Scott Allen designing and coding it :-)
>
>The user's perceived speed in the browser will be based on server trips, so using SPA or SPAish Ajax calls makes a lot of sense to me. Also, the idea of cached objects being used when available seems important.
>
>Have you done Julie's latest Pluralsight course on enterprise EF design yet? I'm still chewing that over but it did answer a lot of questions I had earlier about how all this stuff fits together.
>
>Still don't have it all half figured out but I know I'm having fun :-) and today an old client surfaced after 5 years and I may even get a chance to do a real app with it. That will get the juices flowing :-)