architectural-patterns

Using ActiveRecord you might define a class like this: class Contact { private String _name; public String Name { get { return _name; } set { if (value == String.IsNullOrWhiteSpace()) throw new ArgumentException(...); else _name = value; } } public Boolean Validate() { ... /* check Name is unique in DB */ } public Boolean Save() { ... } public static List<Contact> Load() { ... } } Whilst this is nice and simple, I've found my classes become very bloated with a big mix of logic going on! Using a layered/domain design you might define the same class like: class Contact { [Required

According to Sun and Msdn it is a design pattern. According to Wikipedia it is an architectural pattern In comparison to design patterns, architectural patterns are larger in scale. (Wikipedia - Architectural pattern ) Or it is an architectural pattern that also has a design pattern ? Which one is true ? MVC is more of an architectural pattern, but not for complete application. MVC mostly relates to the UI / interaction layer of an application. You're still going to need business logic layer, maybe some service layer and data access layer. That is, if you're into n-tier approach. Why does one

How do I encapsulate the saving of more than one entity in a transactional manner using the repository pattern? For example, what if I wanted to add an order and update the customer status based on that order creation, but only do so if the order completed successfully? Keep in mind that for this example, orders are not a collection inside the customer. They are their own entity. This is just a contrived example, so I don’t really care whether orders should or should not be inside the customer object or even in the same bounded context. I don’t really care what underlying technology will be

How are Views created in MVP? Does the Presenter always create them (in addition to View in case of subviews)? Or is it a separate third-party component or App or something that creates them? Let's also add that I'm probably going to do this on Dojo Toolkit/ExtJS (JavaScript that is). So, I have these code lines: var v = new MyApp.view.User(); var p = new MyApp.presenter.User(); where should both lines go exactly? Does the presenter instantiate the view, or vice-versa? And what instantiates the first instance? Marijn It depends ... The main goal of MVP is to separate complex decision logic

I've been using MVC for a long time and heard about the " Service " layer (for example in Java web project) and I've been wondering if that is a real architectural pattern given I can't find a lot of information about it. The idea of MVCS is to have a Service layer between the controller and the model , to encapsulate all the business logic that could be in the controller. That way, the controllers are just there to forward and control the execution. And you can call a Service in many controllers (for example, a website and a webservice), without duplicating code. Service layer can be