n-tier-architecture

问题 Update I have looked into various php frameworks (yii framework looks particularly good/interesting) and they seem to offer some very good features compared to simple template engines (including MVC and other features like database integration). I am certain that some from of separation between code and display is needed. Whether that is just plain php (as a template engine), a template engine (e.g smarty) or a framework probably depends a lot on the application and the company/programmers

问题 I'm currently designing the foundation for a large application. We are going with the traditional 3 tier system using EF in the data layer, plain jane c# classes in the business layer and MVC / WCF for the ui layer. We have prototyped enough of the application to realize that this will work for us, however due to the complexity of the business requirements it will be common for some of the business components interact with one another. Consider the following two business components:

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 5 years ago . I'm starting a home website project in PHP and I intend to do it with a 3-tier architecture. But I can't find anything on the standards/preferences of folder structure in such an architecture. The folder structure we use where I work is the following one: (folders are bolded)

问题 I am planning to follow onion architecture for my new application. the solution hierarchy is as follows Domain - where all the interfaces for the services and repositories defined. Infrastructure - this is the layer where all data access is placed. these classes typically implements interfaces defined in domain. Web - this is my presentation part of the application. inside the same layer i have separate for folder for implementing the services defined in domain. My plain is to use Dependency

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 3 years ago . Background We use the Microsoft (.NET) technology stack. We currently have a large monolithic web app. We are planning how to implement Domain Driven Design. We plan to implement microservices on some bounded contexts, but not all. Because it is a monolith, most bounded contexts

问题 I am working hard to standardize one single way of Layered/n-Tiered design of my all applications. I am trying to make all my applications 5 tiered. Code: | UI | | | Business Object | | | OR-Mapper | | | Data Access | | | RDBMS | Suppose I am developing an application with a log-in/log-out capability for users. I am creating 4 projects under a VS2005 solution. Each project is for one of the upper 4 layers. I am designing my Business Object class as follows:- public class User { private string

问题 Assuming the you are implementing a user story that requires changes in all layers from UI (or service facade) to DB. In what direction do you move? From UI to Business Layer to Repository to DB? From DB to Repository to Business Layer to UI? It depends. (On what ?) 回答1: The best answer I've seen to this sort of question was supplied by the Atomic Object guys and their Presenter First pattern. Basically it is an implementation of the MVP pattern, in which (as the name suggests) you start

问题 I recently asked this question: Expose XML or Objects - thanks all for the responses. One point to clarify. The API will always be accessed remotely (i.e. as a service), most probably via webservices or WCF. I agree that in theory a strongly typed API exposing objects as the inputs/outputs is the right way to go. However, I feel that there is still an argument to be made for exposing XML. As I see it the reasons for using XML are: The business rules can be written by business analysts in

问题 In a traditional sense, N-tier means separating the application into "tiers" and putting each "tier" on different servers. This was done for at least 3 reasons: Maintenance: a) Code Maintenance: Easier to do bug fixes and feature additions. b) Hardware Maintenance: Taking one server down does not disrupt service from other tier. Performance: One server was often not fast enough to handle web requests, business logic computations, and database/file access at the same time. Scalability:

问题 How do you pass data to layers in an n-tier application? I have mapped out 3 different methods. A) generic .net objects generic data tables, Hashtables, generic datasets, strings, ints etc... then using the datasets to fill your business objects which get sent to the UI layer. alt text http://img11.imageshack.us/img11/460/generic.png http://dabbleboard.com/draw?b=eiu165&i=26&c=54eef6f1ac01f03c85919518f4a24e798e57e133 Pro- No extra layers needed Con- Have to work with Generic datasets and