design patterns - ASP.net Confusion among web architecture -
a little background:
i started career 5year ago web developer using asp.net , c#, after working web developer year switched world of low level programming (i.e c/c++). now, last 4 years have been working in c/c++
at present have been assigned task develop large scale web application (by large scale mean large number of users in million , huge communication among user communication @ twitter or facebook , huge backend database aswell). since worked in asp , c#, prefer develop application using asp.net , c#
my question:
currently project in requirement gathering phase , in meanwhile assigned task design architecture. google various architecture resources , came across following:
- mvp
- mvc
- three tire architecture (one use 5 year back)
- please mention more, if there exist coz find 3
now totally confused first 2 because site mention if use mvc not allowed use web forms, , many more . . .
secondly sites mention soap , rest feel not able use asp.net , c# (with .net framwork 4.0)
what want
first, appologise in advance coz feel confusion arise because have experience in c/c++ rather web development. secondly, know no 1 did job done me , don't want so, i need guidence i.e start with, resources should study etc.
this site build on mvc.
mvp more suitable older asp.net technology webforms, can pain. 3 tier architecture more overall system architecture have database, service exposing database, , consumers using database. refers when separate app in 3 layers, data, business , presentation. mvc , mvp ui patterns.
now, want tell use, impossible, because have tiny piece of picture. however, prefers mvc , heavily object-oriented practices when designing application, except when put fast made.
the internet full on tutorials on these technologies, should familiarize first them, , decide 1 use.
Comments
Post a Comment