Talk:Multilayered architecture

Suggestions
''Moved from Talk:Common layers in an information system logical architecture due to article merge. -- Beland (talk) 19:46, 15 July 2013 (UTC)''

I think this article is useful, but my opinion is it should focus on three main layers, not four:
 * User interface
 * Business logic
 * Data access / infrastructure

The Service layer exists to open up the object model according to the diagram in the first note. I think this article would add a lot of value by grouping layers into three categories and explaining in principle where, why and how to use each layer.

The user interface layer is made up of two sub-layers:
 * "dumb" forms, screens or webpages
 * controllers for the above

Business logic layer can comprise:
 * Service layer
 * Object model / domain model
 * processes and workflows
 * rules and rule validation

Data access layer can be:
 * Service agents - wrappers to web-services or legacy applications
 * Data access objects - for interfacing with databases, csv and xml files
 * Infrastructure support such as SMS, email, Active Directory

In my opinion the idea of using layers is to simplify and add structure to systems. The layers below have no reliance on the layers above and could be interchanged, re-used or distributed disparately. I just think there are three main groups of layer rather than four. Cosiwiki (talk) 22:05, 18 August 2008 (UTC)
 * Good suggestions. We do have three tiers on Multitier architecture; maybe it would make sense to further merge this article into that one, and just explain the different terminology and possible number of layers or tiers. -- Beland (talk) 19:48, 15 July 2013 (UTC)

✅