jHertel has already given a brief introduction to what MVC is, some questions that can help you about this specifically:

• Where should the business rule be in the MVC standard? (perhaps the most important one to understand here in the question) li>
• Is business model handling a bad practice?
• What is the View in the MVC standard?
• What is MVC (Model, View, Controller)?
• What is MVP and MVVM?
• MVC Alternatives to Web Applications
• How to use MVC in PHP?

From my summary point of view, MVC does not have a specific standard, in fact in many ways you can make use of it and achieve the same result, being strict or not, inphinit is not strict, truth is very "free", with the exception of Controllers which are almost always required (although it supports Closures / a>).

So the MVC is a way to organize and not a technology, from my point of view, the most common MVC represented is this:

<?phpnamespaceModel;classUserextends\Inphinit\Experimental\Model{}

AtthemomentIremovedtheclass\Inphinit\Experimental\Model,notbecauseitiswrong,butbecauseitstilldoesnotachievewhatIexpect,frommypointofview,Modelshavenothingtodowiththedatabase,theyonlyusethedatacontainedinthem,ThepurposeoftheModelistodefinethe"business rules", thus making use of any type of information, having the ability to obtain them, update and delete, but all this having rules.

However, I believe that a Model, wherever it is, should never manipulate things directly, type send data to ouput, or send response, it should only send the response (if any) to the controller and the controller should take care of it. rest (of course I rely on this with the experience I had with totally different tools, as MVC said is not always the same in two different places or frameworks).

In most frameworks I notice the Model is used merely as a tool for connecting to the bank, and some rules end up falling within Controller .

When I designed inphinit it had 5 goals:

With this last goal we have reached namespace Model; and the system/application/Model/ folder, the framework does not have anything like migration , connection and sqlbuilder , but this does not mean that you can not install third-party stuff, there are frameworks that I've even used with it like:

• link
• link
• link
• link (gave a brief explanation here Is there any way to use Laravel Eloquent in the Silex microframework? )

In other words, the focus of the folder and namespace Model is the same as that of most frameworks, however you can use the ORM you want or as desired >

  

As soon as possible irie add a step-by-step one or more frameworks to work with the namespace Model .

  

I'd like to know what the purpose of the Model folder is?

Usually in web applications we use a form of project organization called MVC. ( M odel- V iew- C ontroller)

• Model Classes related to database and business rules

• View Templates with HTML / Template language to view the contents of your application.

• Controller Classes that control the application. It's like a glue between models and views. It is usually in the controllers that the application checks whether it is a GET, POST, etc. and makes the decisions about which View to show, how to process the data, etc.

  

What is the class for the Model folder

In this organization model the classes that correspond to the business rules and connection to the database are usually in the Model folder.

It is a form of organization and you can choose to follow it or not.

  

And how important are these classes in relation to how my Web application works?

The importance of the templates is to make the business and database rules of the rest of the application clearer and separate.

Currently MVC is heavily used in frameworks, although I never see an exactly same or standardized structure. This serves more as a guideline to keep the organization, but you are always free to change and use as needed.