Is it advantageous to use the MVC standard in small applications?

Asked

Viewed 834 times

2

I’ve read several articles related to MVC, its advantages in maintaining reusability codes and everything else.

But the question is, in small applications it is worth using this standard, because from what I understand, have to have a whole planning process when creating an application using this standard.

  • 5

    Responding for my experience, which is little. In the company where I work there was a lot of demand for small projects. Like for example a site where you need an area to edit the site items, something like banner, photos, etc., simple things. When I started using the MVC standard, the development and maintenance of the projects became much faster. I believe it is advantageous yes.

  • Just an opinion, which would be like asking if it’s an advantage to use BDD to develop small applications. For those who do not have the habit can be less productive but, after taking the practice, you become less productive if you do not use

  • 1

    What would be a small application for you?

  • A system that manages the contents of a website; customer registration; account control

  • 4

    I for my experience would use it for quick implementation and easy maintenance, but one of the things that motivate me to use it and easy integration with other team members, as our team here and divided into designers and programmers is very easy to split.

  • 1

    Look depends MUUITO your project, what would be your goals, work with MVC in Rails, for me is a wonder but I only acted in large projects with him. Outside of MVC I worked with Web Forms in C#, (ASP .NET), and several times trying with MVC 3 or 4 / 5 would not be very indicated not, because sometimes it can add unnecessary complexity to your project. So stay tuned and know how to verify the real needs and characteristics of your goal! D

Show 1 more comment

1 answer

11


In my opinion it is true, precisely for the organization and the ease (theoretically) in maintaining the code afterwards. I don’t know if you already develop using some framework that MVC values, but when using these frameworks no matter the size of the application, the idea of using MVC is always there, in small and large applications.

A good example is to develop an application using Ror (Ruby on Rails), MVC is so well applied that there is no escape from the organization of models, views and controllers.

The planning really must exist as you mentioned, but this regardless of whether to use MVC or not, right?

Ah, and as much as we plan well the development of the application, in the labor market everyone knows that time is valuable, suddenly your manager comes up with an amazing idea, you need to change and at that time the championship ran away a lot from your initial planning...

Finally, in a simple and quick response I think it is very worthwhile to maintain the MVC standard even for small applications, because frameworks that help in development always apply the standard.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.