0
Multi-tier Architecture
Posted by Erik Gaius,aka [ K i r E ]
on
Wednesday, February 25, 2009, 11:33 AM
in
Tipz n Trix
Bakit kailangan ng isang software (project) ng isang architecture, or more specifically, Multi-tier Architecture?
Ok, definition muna: multi-tier architecture (often referred to as n-tier architecture) is a client-server architecture in which, the presentation, the application processing and the data management are logically separate processes (Wikipedia)
Isa pa: Normally may three "layers" or tiers sa isang multi-tier architecture: Ung Presentation, ung Business Logic, at Data access layers. Bakit pinag-hiwalay hiwalay? Para madaling palitan. Sabihin nang ung wesite nyo (as ung html) ay na reject, hindi kayo back to zero! Kung hindi pala supported ung database nyo, madaling magpalit nang hindi naapektohan ung Business Logic or Presentation layers.
Let's start with the Data Access Layer: basically, ung nag CRUD (Create-Retrieve-Update-Delete) ng data. Ung business Logic nmn ay ung part ng software na nagproprocess ng information. Lahat ng algorithms, automation at logic na needed pra mag process ng inforamation ay nsa loob ng business logic layer. Keywords: 'needed pra mag process'. Ibig sabihin, ang core functionality (ang mga pyesa na hindi pwedeng mwala sa project mo) ay dapat nsa business logic layer. Everything else, such as pagsasave ng recently opened documents or effects sa user interface ay dapat nsa topmost layer na: ang Presentation Layer - which is the layer na nakikita ng End User, such as the website or the application's user interface.
So, Bakit kailangan ng isang software (project) ng isang architecture, or more specifically, Multi-tier Architecture? Dahil pinapadali nito ang pag mamanage ng project by splitting it into modules na madaling palit-palitan. ^^ Gets?
Ok, definition muna: multi-tier architecture (often referred to as n-tier architecture) is a client-server architecture in which, the presentation, the application processing and the data management are logically separate processes (Wikipedia)
Isa pa: Normally may three "layers" or tiers sa isang multi-tier architecture: Ung Presentation, ung Business Logic, at Data access layers. Bakit pinag-hiwalay hiwalay? Para madaling palitan. Sabihin nang ung wesite nyo (as ung html) ay na reject, hindi kayo back to zero! Kung hindi pala supported ung database nyo, madaling magpalit nang hindi naapektohan ung Business Logic or Presentation layers.
Let's start with the Data Access Layer: basically, ung nag CRUD (Create-Retrieve-Update-Delete) ng data. Ung business Logic nmn ay ung part ng software na nagproprocess ng information. Lahat ng algorithms, automation at logic na needed pra mag process ng inforamation ay nsa loob ng business logic layer. Keywords: 'needed pra mag process'. Ibig sabihin, ang core functionality (ang mga pyesa na hindi pwedeng mwala sa project mo) ay dapat nsa business logic layer. Everything else, such as pagsasave ng recently opened documents or effects sa user interface ay dapat nsa topmost layer na: ang Presentation Layer - which is the layer na nakikita ng End User, such as the website or the application's user interface.
So, Bakit kailangan ng isang software (project) ng isang architecture, or more specifically, Multi-tier Architecture? Dahil pinapadali nito ang pag mamanage ng project by splitting it into modules na madaling palit-palitan. ^^ Gets?
Post a Comment