MVC Pattern: Usage Best Practices

Question

I am striving to respect the best I can the MVC pattern. It simplifies the life of a developer (or devs) a lot. The thing that I am wondering about is how to load multiple sections at a time.

To make it clear, I am going to take the example of a to-do list (it's pretty used this days). Let's say there are project -> milestones -> tasks.

What we need:

get them all - all the projects with all the milestones with all the tasks in a nested json encoded array.
get only the projects
get only the milestones
get only the tasks

For the last three, we can have separate controllers that provide us with the corresponding data. The problem shows up when we try to "get them all" in a nested json-encoded array.

What is probably the best way to handle that?

I thought of a few possibilities:
- Move the project, milestone and task generators in helper classes - this means we call them from the individual controllers and also call them when we need to get them all
- From the view of the projects, call the controller/view of the milestones (of each project) [which in turn calls the controller/view of the tasks (of each milestone)]. This might look like a simulation of 3 requests in 1.

The motivation comes from the fact that while I could fetch all the projects and then the milestones of each and then the tasks of each milestone, it would take a lot of requests. If we could get all the calls in one, it would take considerably less time to get the data, let alone that in one request the data is more organized.

Are you really referring to MVC design pattern, or you actually are talking about Asp.NET MVC framework? Either your title or tags are wrong. — tereško
– tereško, Commented Oct 1, 2012 at 12:14
@tereško I am talking about any framework that implements the MVC pattern. — Andrew
– Andrew, Commented Oct 1, 2012 at 17:45

Faris Zacina · Accepted Answer · 2012-09-30 10:02:23Z

1

You definitely need to separate the data access concern into a logical layer that can be accessed from different controllers.

If you are willing to go down the DDD path, than it would make sense to identify your domain objects (Project, Task etc.), aggregate roots and then build repositories for data access. You can reuse the repositories (e.g. ProjectRepository, TaskRepository) in different controllers and the repository itself will be the unit of reuse that will allow you to get data from multiple controllers using the same interface. You can also leverage a unit of work if you need to get data from multiple repositories from the same controller efficiently.

If you are not going down the DDD path you can use an ActiveRecord pattern (like in Ruby on Rails) that will be a in-memory representation of a database record. This would be probably pretty simple to implement if you are using a relational SQL database.

I think that the Project in your case is the aggregate root, and that means you would have only one repository (ProjectRepository). That repository would have an operation to get all the projects and fetch all associated data (Milestones etc.) and that would be a fast operation optimized as close as possible to the data source (store procedure?). On the controller itself you would use the objects retrieved and serialize/encode to JSON.

edited Sep 30, 2012 at 10:02

answered Sep 30, 2012 at 9:50

Faris Zacina

14.3k8 gold badges64 silver badges76 bronze badges

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

2 Comments

Andrew Over a year ago

The DDD path is more object oriented than the AR pattern would be, right?

Faris Zacina Over a year ago

both are object-oriented.. however the DDD path is a higher abstraction over the data storage. The DDD path is closer to the real world definitely, and then under the hood you can store your data anywhere (SQL, File, Network..etc.)

user2626270 · Accepted Answer · 2013-09-11 00:30:09Z

0

Make 3 independent JSON requests from browser. Don't worry. If you turn on Firebug, and open mail.google.com - you will see there more than 40 requests.

answered Sep 11, 2013 at 0:30

user2626270

2582 silver badges6 bronze badges

Collectives™ on Stack Overflow

MVC Pattern: Usage Best Practices

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related