Using the Specification Pattern
- by Kane
Like any design pattern the Specification Pattern is a great concept but susceptible to overuse by an eager architect/developer.
I am about to commence development on a new application (.NET & C#) and really like the concept of the Specification Pattern and am keen to make full use of it. However before I go in all guns blazing I would be really interested in knowing if anyone could share the pain points that experienced when use the Specification Pattern in developing an application.
Ideally I'm looking to see if others have had issues in
Writing unit tests against the specification pattern
Deciding which layer the specifications should live in (Repository, Service, Domain, etc)
Using it everywhere when a simple if statement would have done the job
etc?
Thanks in advance