c# - Developing application with three layers and two tier -
as fas have understood can 3 layered architecture means seperate projects each concern. ui layer, business layer , data layer. ui talks bl , bl talks db , vice versa. that's maintainability , idea of seperation of concerns reasonable. on other hand, tiers different layers. namely, tiers directly related machines/network. mean when 2 tier, client machine , database server machine. when 3 tier, client machine, application server machine , database server machine. in terms of these information developing 2 tier application uses 3 layer architecture possible.
so far, have used 3 layer time decide whether should develop in 3 tier or 2 tier. there windows form project in field , around 150 clients , 100 hand terminals using windows form project , communicate on web services. in hand terminals, obvious best solution using 3 tier windows clients running on windows 7, hard decide whether should talk database on 1 application server or directly connecting database.
main question here benefits of 3 tier architecture on 2 tier. me 1 more tier means 1 more server/host/machine needs , running time may overhead.
please guide choosing best tier architecture.
i recommend using '3 tier' (client, application server, , database server) if you're going doing major task on application server otherwise consume resources available run database platform. example, connection pooling or connection management software running in between application (business layer) , database server (data layer).
Comments
Post a Comment