In the context of the repository pattern, aggregate roots are the only objects your client code loads from the repository. The repository encapsulates access to child objects – from a caller’s perspective it automatically loads them, either at the same time the root is loaded or when they’re actually needed (as with lazy loading). For … Read more
You’re referring to any framework that implements one of the many MV* (as in, model-view-wildcard) design patterns. There’s MVC (model-view-controller), MVVM (model-view-view model), MVP (model-view-presenter), and probably some more. The * is just a wildcard, not something specific. Read up on it here: http://www.infragistics.com/community/blogs/nanil/archive/2013/04/01/exploring-javascript-mv-frameworks-part-1-hello-backbonejs.aspx
On my quest for the truth I discovered that there are actually very few “acceptable” reasons to use a Singleton. One reason that tends to come up over and over again on the internets is that of a “logging” class (which you mentioned). In this case, a Singleton can be used instead of a single … Read more
With design patterns, there usually is no “more advantageous” solution that works for all cases. It depends on what you need to implement. From Wikipedia: Builder focuses on constructing a complex object step by step. Abstract Factory emphasizes a family of product objects (either simple or complex). Builder returns the product as a final step, … Read more
What makes you say that either a singleton or a static method isn’t thread-safe? Usually both should be implemented to be thread-safe. The big difference between a singleton and a bunch of static methods is that singletons can implement interfaces (or derive from useful base classes, although that’s less common, in my experience), so you can pass … Read more
The Difference Between The Two The main difference between a “factory method” and an “abstract factory” is that the factory method is a method, and an abstract factory is an object. I think a lot of people get these two terms confused, and start using them interchangeably. I remember that I had a hard time … Read more
I don’t actually think that DI/IoC are that uncommon in Python. What is uncommon, however, are DI/IoC frameworks/containers. Think about it: what does a DI container do? It allows you to wire together independent components into a complete application … … at runtime. We have names for “wiring together” and “at runtime”: scripting dynamic So, a DI container is nothing … Read more
I don’t actually think that DI/IoC are that uncommon in Python. What is uncommon, however, are DI/IoC frameworks/containers. Think about it: what does a DI container do? It allows you to wire together independent components into a complete application … … at runtime. We have names for “wiring together” and “at runtime”: scripting dynamic So, a DI container is nothing … Read more
In general, a wrapper class is any class which “wraps” or “encapsulates” the functionality of another class or component. These are useful by providing a level of abstraction from the implementation of the underlying class or component; for example, wrapper classes that wrap COM components can manage the process of invoking the COM component without … Read more