3-tier

问题 There are so many types of diagrams in UML. I am little confused about which one to use for what. I designed a 3-tier architecture for my web application software using UML Component Diagram. Please see the attached image and tell me if I'm doing this right or wrong. Is this a good idea to use Component Diagram for this architecture? 回答1: Basically I agree with @KeizerHarm's answer. However, there's a flaw in your diagram. Rather than packages you should use components since you put ports on

问题 I am working on Web API Core 2.2 and need to design 3 tier architecture. How can I do it. My Project Structure as below In Web API Project.. public void ConfigureServices(IServiceCollection services) { services.AddDbContext<HrmsDbContext>(opt => opt.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"))); } In DAL (Library project, I have made my DBContext and provided connectionstring like below. Is there any better so that I had not provide connectionstring at two places? and

问题 I am working on Web API Core 2.2 and need to design 3 tier architecture. How can I do it. My Project Structure as below In Web API Project.. public void ConfigureServices(IServiceCollection services) { services.AddDbContext<HrmsDbContext>(opt => opt.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"))); } In DAL (Library project, I have made my DBContext and provided connectionstring like below. Is there any better so that I had not provide connectionstring at two places? and

问题 Just began researching mvc, and am not sure I grasp it yet. From what I gather it seems like an implementation of a 3 tier solution ie Model corresponds to DAL, Controller to business logic layer, and View as Presentation layer. Am I way off base here? 回答1: I caution against treating the Model as simply a data access layer. That's oversimplifying, and it results in you putting too much code into the Controller Layer. It's better if you put more of that code in the Model, and make database

问题 Just began researching mvc, and am not sure I grasp it yet. From what I gather it seems like an implementation of a 3 tier solution ie Model corresponds to DAL, Controller to business logic layer, and View as Presentation layer. Am I way off base here? 回答1: I caution against treating the Model as simply a data access layer. That's oversimplifying, and it results in you putting too much code into the Controller Layer. It's better if you put more of that code in the Model, and make database

问题 Just began researching mvc, and am not sure I grasp it yet. From what I gather it seems like an implementation of a 3 tier solution ie Model corresponds to DAL, Controller to business logic layer, and View as Presentation layer. Am I way off base here? 回答1: I caution against treating the Model as simply a data access layer. That's oversimplifying, and it results in you putting too much code into the Controller Layer. It's better if you put more of that code in the Model, and make database

问题 I am not using any ORM. So I am having a debate whether "Save" method actually belongs to a Business Domain entity or should be abstracted in some service that will be handed over the Business Domain Entity for saving ? e.g. class Employee { string Name; DateTime Birth; GetAge() { } Save() { } } OR class Employee { string Name; DateTime Birth; GetAge() { } } SomePersistenceService { Save(Employee emp) { } } 回答1: Since this question is tagged with 'domain-driven-design', you'll need a

问题 I am not using any ORM. So I am having a debate whether "Save" method actually belongs to a Business Domain entity or should be abstracted in some service that will be handed over the Business Domain Entity for saving ? e.g. class Employee { string Name; DateTime Birth; GetAge() { } Save() { } } OR class Employee { string Name; DateTime Birth; GetAge() { } } SomePersistenceService { Save(Employee emp) { } } 回答1: Since this question is tagged with 'domain-driven-design', you'll need a

问题 I've been in the process of re-writing the back-end for a web site and have been moving it towards a three-tiered architecture. My intention is to structure it so: Web site <--> WCF Service (1) <--> Business Layer (2) <--> Data Layer (3) My issue is with the placement of the DTO's within this structure. I'll need to use DTO's to move data between the business layer and the WCF service and from the WCF service to the consuming web site. During my research on here I've read some excellent

问题 Conversions can be done in the first layer ( UI ) ? 回答1: For these kind of operations I personally create a Utils class/namespace under project namespace ( myProjectNamespace.Utils ). A ststic class with public static members for conversions, formatting, calculations... Put this class in BLL (Business Logic Layer) most of the time but sometimes you need different Utils for different layers. 回答2: Assuming an image is an input - inputs usually come into a system through: The frontend interface