Search code examples
design-patternsmodel-view-controllerarchitecture3-tier

Does anyone use plain old 3 tier architecture?


So I've been learning about architectural styles and patterns. From what I can see, when it comes to 3-tier architecture, most people are using a pattern (such as MVC for example). But my question is, does anyone just use a plain old 3-tiered, bi-directional architecture without any patterns? Is that practiced or even acceptable in industry?


Solution

  • The Architecture should

    Form Consistent

    layers, as described in the Code Complete, 2nd Edition. Having just any of the architectural patterns and styles (MVC is actually a part of the Multitier architecture's Business tier) won't be enough. Depending from the requirements this

    plain old 3-tiered bi-directional architecture

    could be the best fit for a Client-server distributed system. Remember - Overdesign is bad as much as no design at all.

    So as a bottom line - keeping the good practices, SOLID principles and design patterns at all levels, is what makes the good software.

    design levels