Application review: Northwind Starter Kit

i continue to try to find a sample application for northwind to use as my contrasting example for an article that i am writing, and i found the northwind starter kit project. even the project summary page gave me a few twitches, here is a small piece with the twitch inducing stuff bolded:

the application has been designed using common patterns , such as the ones defined within the "classic" " designs patterns " by erich gamma et al. and " pattern of enterprise application architecture ", by martin fowler; though not required, these lectures are strongly recommended.

guys! this is northwind , the likelihood that you’ll need design patterns to build this application is nil to none! that just screens complexity overload.

domain logic is implemented by means of a domain model , onto a layer of services adds application logic . the model is persisted by a dal designed around the principles of the " repository " patterns, which has been implemented in a linq-friendly way.

northwind is a crud app, at its core, all of those things are adding complexity, and they aren’t really adding much at all. in fact, they are going to create just noise, and make working with things that much harder.

and then i opened the project, and i got this:

i mean, really ? seriously?!  22(!) projects to do a sample application using northwind?

this is the point where i gave up on this as something that could be useful, but here are a few other gems as well:

i really like how the update method does what it is meant to do, right?

note that in either implementation, we are looking at totally and drastically different behavior.

let us look at the interface, too:

the design is straight out of patterns of enterprise application architecture, and it is totally the wrong design to be using if you are using a modern or/m.

seriously, this is northwind we are talking about, why make things so freaking complex?!