To summarise the flow, in response to a request from your web app you, maybe call a method in your business layer which then calls to its relevant service to get the data. Depending on whether the data to reply is on database or remote; the service will
make a request to another API or use a repository to call in to the database and return the result back up the chain.
So your BLL does not have any dependency on things like Json.NET or HttpClient. Your Services layer is encapsulating that.
Also your services layer does not have any dependency on database related assemblies like EF or System.Data. DAL is encapsulating that.
in response to a request from your web app you, maybe call a method in your business layer which then calls to its relevant service to get the data. Depending on whether the data to reply is on database or remote; the service will make a request to another
API or use a repository to call in to the database and return the result back up the chain
Are you sure about that? Isn't the service supposed to sit between the web application and the BLL?
Member
3 Points
11 Posts
N-Tier Architecture plus SOA
Jan 18, 2015 02:49 AM|AbhiFindingForAnswer|LINK
Can we have n-Tier Architecture with SOA implemented , for Web applications with WCF
if Yes , How can we justify it OR in which scenario we can use this
and in which tier we can have WCF Services/web Services.
Participant
1231 Points
375 Posts
Re: N-Tier Architecture plus SOA
Jan 18, 2015 03:06 AM|IbrahimIslam|LINK
It can look like this:
MyApp.Web (ASP.NET MVC) -> MyApp.BLL (Business logic) -> MyApp.Services (Calls to remote services, db, etc.) -> MyApp.DAL (EF, UnitOfWork/Repositories etc)
To summarise the flow, in response to a request from your web app you, maybe call a method in your business layer which then calls to its relevant service to get the data. Depending on whether the data to reply is on database or remote; the service will make a request to another API or use a repository to call in to the database and return the result back up the chain.
So your BLL does not have any dependency on things like Json.NET or HttpClient. Your Services layer is encapsulating that.
Also your services layer does not have any dependency on database related assemblies like EF or System.Data. DAL is encapsulating that.
Member
3 Points
11 Posts
Re: N-Tier Architecture plus SOA
Jan 18, 2015 07:57 AM|AbhiFindingForAnswer|LINK
Thanks IbrahimIslam ,
how layers will get changed if we put data warehouse tool for which we push/pull data through services along with database in the same application.
will that come under data layer or service layer?
Participant
1231 Points
375 Posts
Re: N-Tier Architecture plus SOA
Jan 18, 2015 12:23 PM|IbrahimIslam|LINK
I did not understand your question clearly but anything to do with database should end up in DAL.
Member
40 Points
60 Posts
Re: N-Tier Architecture plus SOA
Feb 02, 2015 10:55 AM|Ringoo|LINK
Are you sure about that? Isn't the service supposed to sit between the web application and the BLL?