How do you go about creating a "logic tier" (probably in .Net)? [View all]

Last edited Wed Apr 2, 2014, 08:13 AM - Edit history (1)

I think we need a logic tier where business objects can reside, like Customers, Orders, etc, so that they do not have to be constantly reinvented every time a request comes along. I've grown fond of OOP and if it's not the correct and modern approach to coding, I'd love to be convinced to go back to the linear procedural style if that will make me fit in better. But for now it just seems like OOP is the way coding is supposed to be done, if I'm not mistaken. I'm not sure how to make people start learning OOP, but I've been given the green light and going to see what happens.

We have multiple skills sets, both open source and .Net, and I primarily use .Net and the MVC design pattern. Would creating a logic tier involve creating a project named something like "Logic Tier" and publishing it to an IIS server and exposing it in the form of WCF, for instance? I've already got a contracts.cs file with interfaces in it, and a services.cs file. I have those in one project that I'm sharing among two solutions at the moment. Should those be turned into a WCF project? I've seen very lengthy descriptions of architectures, but would like to know if this WCF approach would be a reasonable way to just get started with a basic logic tier, or if there is another way.

Also, are stored procedures considered part of the logic tier, and if not, how do you decide whether to put code in SPs vs the LT?