How the communication between three layers is happening?
-
I have a question: Suppose my application is having a three layer architecture, contains UI Layer, Business Layer & Data Layer. Now think that, these three layers can be build and deployed seperately. Now my question is, how the communication between the UI layer and Business Layer or BusinessLayer and Data Layer be happen? In other words, if there is a method in Buisness Layer class referenced in UI Layer, how the UI Layer should know it should call the particular class in Business Layer? :doh: Is it happen through WebServices? Would be great if any article relating to this subject. Regards meeram395 :^)
Success is the good fortune that comes from aspiration, desperation, perspiration and inspiration.
-
I have a question: Suppose my application is having a three layer architecture, contains UI Layer, Business Layer & Data Layer. Now think that, these three layers can be build and deployed seperately. Now my question is, how the communication between the UI layer and Business Layer or BusinessLayer and Data Layer be happen? In other words, if there is a method in Buisness Layer class referenced in UI Layer, how the UI Layer should know it should call the particular class in Business Layer? :doh: Is it happen through WebServices? Would be great if any article relating to this subject. Regards meeram395 :^)
Success is the good fortune that comes from aspiration, desperation, perspiration and inspiration.
Web Services, Sockets, Named Pipes, MSMQ, they can communicate through whatever means is most applicable to your scenario. There isn't one technology that fits all problems, you have to look at your problem and figure out which technology solves it best.
meeram395 wrote:
how the UI Layer should know it should call the particular class in Business Layer?
There needs to be some coupling between the two layers to make this happen. Inside the UI layer there's a distinction between what is displayed and how it's displayed. The what is the part that's coupled to the rest of the system - it's the information that's sent to and from the service/business layer to so it's job. This is where the UI layer needs to know what the rest of the system does. How it displays it is totally up to the UI layer, that's the part that's completely independent from the rest of the business logic. The basic designs to separate these parts inside the UI layer are MVC, MVP and MVVM. Here's[^] a quick and dirty on those.
:badger:
-
Web Services, Sockets, Named Pipes, MSMQ, they can communicate through whatever means is most applicable to your scenario. There isn't one technology that fits all problems, you have to look at your problem and figure out which technology solves it best.
meeram395 wrote:
how the UI Layer should know it should call the particular class in Business Layer?
There needs to be some coupling between the two layers to make this happen. Inside the UI layer there's a distinction between what is displayed and how it's displayed. The what is the part that's coupled to the rest of the system - it's the information that's sent to and from the service/business layer to so it's job. This is where the UI layer needs to know what the rest of the system does. How it displays it is totally up to the UI layer, that's the part that's completely independent from the rest of the business logic. The basic designs to separate these parts inside the UI layer are MVC, MVP and MVVM. Here's[^] a quick and dirty on those.
:badger:
-
Thanks Jimmanuel, Thanks a lot. This fully answers my query. And thank you for the article.:thumbsup:
Success is the good fortune that comes from aspiration, desperation, perspiration and inspiration.