architectural-patterns

What is the difference between an 'Abstraction' and a 'Facade'? Is there a difference at all? Or are the terms interchangeable? The facade pattern is an simplified interface to a larger, possibly more complex code base. The code base may be a single class, or more. The facade just gives you a simple interface to it. Abstraction , is used to represent a concept, but not to be bound to any specific instance. (Ie: An abstract class). This doesn't imply simplifying (like the facade pattern does), but rather making a 'common' interface or representation. Facade is a specific design pattern, meant

I have debated this for a while now and still have not come to a conclusion. While most examples I see have the factories code in the application layer I tend to think it should be in the domain layer. Reasons for this: I sometimes have initial validation done in my factory where I want all creation of objects to go through. I want this code to be used on all instantiates of my object. Sometimes an operation requires parameter information which feels unnatural to pass to a constructor. And a few more not as important reasons. Are there reasons why this is a bad practice? Does this break other

In Software Architecture - Foundations, Theory and Practice , I can find definitions for both. The problem is that I don't get what each one of them means in plain English: Architectural Pattern An Architectural Pattern is a named collection of architectural design decisions that are applicable to a recurring design problem parameterized to account for different software development contexts in which that problem appears. Architectural Style An Architectural Style is a named collection of architectural design decisions that (1) are applicable in a given development context, (2) constrain

If i have two objects, namely Fruit' and Color` and their definitions are as follows: public class Fruit { public int FruitId { get; set; } public string Name { get; set; } public Color Color { get; set; } } public class Color { public int ColorId { get; set; } public string Name { get; set; } } How do I bind a collection of Fruit (e.g. List<Fruit>) to a DataGridView? where the resulting output would be something similar to the following: +-----+--------+----------+ | Id | Name | Color | +-----+--------+----------+ | 10 | Apple | Red | | 20 | Orange | Orange | | 30 | Grapes | Violet | +-----+-

Can anyone recommend good tutorial, implementation or sample code on Query object pattern usage, in C#(Java...)? I haven't found much with google. With LINQ being almost everywhere, are you sure you need to reimplement the Query Object ? Basically, you can treat all classes from System.Linq.Expressions to be a good implementation of a Query Object pattern. From Chad Myers: Part 1: http://www.lostechies.com/blogs/chad_myers/archive/2008/08/01/query-objects-with-the-repository-pattern.aspx I suggest Martin Fowler's Query Object Pattern ( http://martinfowler.com/eaaCatalog/queryObject.html ). Get