Generally speaking in a MVC framework we have the Controllers that do things like making sense of a request, preparing the parameters and starting an action in the business logic through some kind of entry point.The business logic is where the real application is described and it's usually defined in terms of services, models and plain classes.My question is, what is in your opinion the correct way to build some entry points for the business logic? Creating some services or plain classes offering the methods? Implementing some static methods in the models?
In a MVC application, what is the correct way to organize the entry points for the business logic?
web development;mvc
Model-View-Controller is primarily a User-Interface paradigm.  It doesn't have much to say about your business logic.  Rather, MVC provides separation of concerns between your business logic and the user interface via Views, Controllers and (sometimes) ViewModels. All business logic concerns are deferred to the Model.  The Model can be architected any way you want.  You said it yourself:  it's usually defined in terms of services, models and plain classes.  If you want a more formal expression of your entry points, create an abstraction layer that has the services, models and plain classes on one side, and methods that embody business processes and transactions (e.g. TransferMoney) on the other side.