M
Marco Pais
Hello.
This post is long, but I think that's a pertinent question for many people.
I built a client/server application using .NET and SQL server, a 2 tier
application. This first version was built in a rush, so its architecture is
not well designed for the company growth.
Some weeks ago, I decided to separate the data from the presentation tier
and include the so named Business Logic Layer. This is a pretty name. and I
can understand pretty well its value. My goal is to facilitate the change of
processes, with transparency to the client. This is one of the
interpretations of SOA.
What did I use for this layer? Web Services. This WS access database through
the call of Stored Procedures. My headaches started here. Is this a good
solution?
I read and I'm still reading several points of view. the are a lot of
opinions J
Concerning the technology used, I am also very confused. This company has
several connected processes. So I built a single class in a WS with several
methods (business services), so those processes can connect through the use
of those services/methods.
For instance I have a CAR. There's a method to get car data from database,
and another one to update car data. Two methods. You will say: use a CAR
OBJECT with appropriate methods. That's were I have some doubts. I can only
have one class in a web service, right? At least, that's what WS config
says:
<%@ WebService Language="C#" CodeBehind="~/App_Code/Service.cs"
Class="Service" %>
What are the best practices? Where can I find better resources for this kind
of development?
Thanks in advance. Sorry the long post.
Regards,
Marco
This post is long, but I think that's a pertinent question for many people.
I built a client/server application using .NET and SQL server, a 2 tier
application. This first version was built in a rush, so its architecture is
not well designed for the company growth.
Some weeks ago, I decided to separate the data from the presentation tier
and include the so named Business Logic Layer. This is a pretty name. and I
can understand pretty well its value. My goal is to facilitate the change of
processes, with transparency to the client. This is one of the
interpretations of SOA.
What did I use for this layer? Web Services. This WS access database through
the call of Stored Procedures. My headaches started here. Is this a good
solution?
I read and I'm still reading several points of view. the are a lot of
opinions J
Concerning the technology used, I am also very confused. This company has
several connected processes. So I built a single class in a WS with several
methods (business services), so those processes can connect through the use
of those services/methods.
For instance I have a CAR. There's a method to get car data from database,
and another one to update car data. Two methods. You will say: use a CAR
OBJECT with appropriate methods. That's were I have some doubts. I can only
have one class in a web service, right? At least, that's what WS config
says:
<%@ WebService Language="C#" CodeBehind="~/App_Code/Service.cs"
Class="Service" %>
What are the best practices? Where can I find better resources for this kind
of development?
Thanks in advance. Sorry the long post.
Regards,
Marco