Re: Web Services/SOA

Tech-Archive recommends: Speed Up your PC by fixing your registry

Marco Pais wrote:
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?

No.

SOA is about exposing services. Web service calls used between the
business logic layer in one app and the business logic layer in
another app.

Web services are not in general suitable for presentation
layer - business logic layer or business logic layer - data
access layer.

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.

A service will consist of a single class that offers one or more
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:

As explained above then GetCar and SaveCar is usually not a good
service.

The car app does all the basic CRUD stuf internally and
expose a service to other apps for stuff like getting values
to the accounting app and reserve car for employee in the
HR app.

Arne
.

Relevant Pages

  • COM+ and a distributed app
    ... business logic layer ... data access layer ... I have decided to separate the BLL from the DAL so I'll be able to locate ... can't I make all these project in one dll/COM+ app ?? ...
    (microsoft.public.dotnet.distributed_apps)
  • COM+ and a distributed app
    ... business logic layer ... data access layer ... I have decided to separate the BLL from the DAL so I'll be able to locate ... can't I make all these project in one dll/COM+ app ?? ...
    (microsoft.public.dotnet.framework.component_services)