if i’m doing c# web api, what is the design pattern for it? Is it mvc?

Sanjay Kumar

Hi, may i know, if i’m doing c# web api, what is the design pattern for it? Is it mvc? Or mvvm?

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Rijwan Ansari5y ago
Accepted answer
It depends upon coding pattern you are following.
For example:
If you are using database model binding in return or reponse then MVC
If you are using ViewModels of each response then MVVM.

The basic MVCVM guidelines we follow are:
Views display a certain shape of data. They have no idea where the data comes from.
ViewModels hold a certain shape of data and commands, they do not know where the data, or code, comes from or how it is displayed.
Models hold the actual data (various context, store or other methods)
Controllers listen for, and publish, events. Controllers provide the logic that controls what data is seen and where. Controllers provide the command code to the ViewModel so that the ViewModel is actually reusable.

https://stackoverflow.com/questions/667781/what-is-the-difference-between-mvc-and-mvvm
Sanjay Kumar5y ago
Thanks bro
Satya Karki5y ago
Hi,
In mvvm, we basically, use separate viewmodel for data binding into views or api response. The viewModels are not use for database communications i.e. they are not database models.
Salman Beg5y ago
Hey it's a mvc but does not contain v(or view) in it. For view you need to use some other technologies like react,vue or other etc. Below is a link which explains what is the exact difference between mvc and mvvm.

https://www.guru99.com/mvc-vs-mvvm.html