Is angular2 mvc?

Question

I have worked in Angular 1.It clearly had a controller which acted as a mediator between View and Model. I realized that in Angular 2 we don't have any controller as such.

So can we still call Angular 2 as an MVC framework?. I know MVC is a design pattern and you implement it in any language. But, with respect to Angular 1, I heard from many that it is an MVC framework, and most of the examples that I saw clearly said that Angular 1 is MVC and Controller separates Model from View. So, I was wondering, now that have Components in Angular2, can we still call it as MVC? Or as Components by themselves follow MVC paradigm, because I do see that in each Component we do separate View and Data and use binding, maybe we can still call it as an MVC.

Not that this is much help, but I think it's referred to as an MV* (or MVWhatever) framework, so you have some license in how to implement the last part. — lintmouse
The angular2 documentation has a great overview of the architecture. It can be found here: angular.io/docs/ts/latest/guide/architecture.html. Although Angular2 is component based you still have separate views, separate scopes for your views, and services that allow you to connect to your backend. — user2263572
I would definitely consider Angular2 MVC. Services would be your model, Components are a mix of Controller and View. You put most of your function logic and "Controller" functions within your class, and attach your view to it via templating. — Morgan G
Follow the link for explanation: how-mvc-pattern-can-be-explained-in-angular — Vishal Singh
@Morgan G Services are definitely not the model. In all MVC related frameworks (including MVVM etc) you have 2 models. The 1st is the domain model. The second is the model that adapts the domain model to the view. In MVVM this is the ViewModel. Many people have also started to use the term ViewModel in straight MVC. — gusgorman

binariedMe binariedMe · Accepted Answer · 2016-03-03T05:59:45

Angular 2 is more of a component based architecture. You can assume everything as component, like directives, services and so on. While directives and services are actually for the support of base components, they are also defined in a similar fashion. A base component contains dependencies, view details and a class declaration which may be considered as controller. So, a well defined component contain one set of MVC architecture.

for example (angular 2 alpha version) :

import {Component, View, bootstrap, provide, NgClass} from 'angular2/angular2';

@Component({
  selector : "my-home"
})

@View({
   directives : [NgClass, EditSettingPanel],
   styles: ['.hidden{ display : none} .visible{ display : block}'],
   templateUrl : "views/blog-panel.html"
})
export class home {
}

}

In the above example you can see that class "home" may be assumed as controller, View is written with @View decorator. The component customization is given by @component decorator. Also you can see different dependencies injection practice.

EDIT :: Example (Current angular 2/4 version)

import { Component } from '@angular/core';

@Component({
  selector: 'custom-component',
  templateUrl: './template.html',
  styleUrls: ['./style.scss'],
})
export class CustomComponent {}

In a nutshell, angular 2 is a component based MVC framework.

Is angular2 mvc?

3 Answers