ASP.NET MVC AJAX Database update - ViewModel vs Controller

Question

I've currently got a controller which passes a model to a view. The view will be making AJAX calls to the controller to make updates to the data rather freqeuently, and the model makes for a rather nice arrangements to make these updates.

I know that making changes to the database in the controller is bad form, and I would like to avoid doing it. However, creating a model on every call and handing the update data off to it, although it seems more correct to me, takes longer on each request, as the model needs to be initialized. Since the user is blocked from interaction with certain elements on the page during the update, this time can really add up across dozens of updates.

Which method is best? Simply making the updates in the controller to keep the application as interactive as possible, or initializing an instance of the model on every request to handle the update at the expense of speedy request processing?

Hector Correa · Accepted Answer · 2011-08-15 14:03:17Z

1

I would suggest optimize your model and/or create a lighter version of it.

Why is your model taking too long to initialize? Is the initialization loading things that you don't need when called in this particular case?

Bottom line, I would move the saving logic to a model but would make sure the model is fast and optimal.

answered Aug 15, 2011 at 14:03

Hector Correa

26.7k8 gold badges61 silver badges76 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ASP.NET MVC AJAX Database update - ViewModel vs Controller

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related