Best design for a “Command Executer” class
Sorry for the vague title, I couldn’t think of a way to condense the question.
Design for a plugin based application [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. I am working on application, details of which […]
Pattern remote facade AND separated Interface
I’m studying design patterns for an exam and I’m stuck on a question:
DDD: service contains two repository
Does it correct way to have two repository inside one service and will it be an application or domain service?
Constant values in the interface
Some time ago I have read two different books and each of them gives totally different answer for the question if it is a good pattern to define constant values in the interface (in java).
Adhering to a protocol and being a subclass at the same time?
In objective C, I have a situation where I would like to have an abstract protocol (interface) with 5 methods and 4 properties, but at the same time, I’d like to have a common implementation of 3 of those 5 methods.
DDD: Service or Repository
I am developing an app in DDD manner. And I have a little problem with it.
What is the best approach to solve a factory method problem which has to be an instance?
I have to add new funcionality in a web service legacy project and I’m thinking what is the best approach for a concrete situation.
Microkernel architectural pattern and applicability for business applications
We are in the business of building customizable web applications. We have the core team that provides what we call as the core platform (provides services like security, billing etc.) on top of which core products are built. These core products are industry specific solutions like telecom, utility etc. These core products are later used by other teams to build customer specific solutions in a particular industry.
Has the emerging generation of programmers got the wrong idea about design patterns?
Over the years I’ve noticed a shift in attitude towards design patterns, particularly amongst the emerging generation of developers.