Re: Just tell me why ? so confuse...

Peter,

I have to disagree with your assesment that when you have total control over
the entire application, that a proprietary solution is best. I'm not sure
why you say that "it is usually recommended" to do this and that "the
recommended solution" is to go that way.

In my experience, working for large enterprises, I find just the opposite.
Even though these companies do have total control over the entire
application (intranet applications), they do NOT want to buy into a 100%
proprietary solution to connect the presentation layer to the services
layer. In fact, they (again, in my experience) want to make the
presentation to services connection as non-proprietary and as
platform-independant as possible (web services) to allow them scalability
and flexibility in the future.

Now, on the back end is a different story... Connecting a web service to a
business layer and that business layer to a data layer, is very often done
with 100% proprietary techniques.

IMHO
-Scott

"Peter Kelcey" <Peter.Kelcey@xxxxxxxxx> wrote in message
news:1131655982.297085.213650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Serge,
>
> It is true that web services can sometimes be the wrong technology to
> use when accessing data. However, there are other times when they are
> the best solution. It depends on what you are trying to achieve with
> your solution. I'll try to explain.
>
> Web services and service oriented architectures are often used in the
> wrong places by people designing applications. This usually occurs when
> people use web services to connect a presentation layer to their
> business or data layers within the same application. Web services are
> based on "open" and vendor independent technologies such as XML, HTTP
> and SOAP. Therefore they offer the best solution for interoperability,
> but they do trail far behind other technologies in terms of
> performance. Proprietary technologies such as .NET remoting take
> advantage of a lot of performance boosts that web services can't.
> Therefore, when you have control of the entire application from
> presentation layer through to business and data layers, it is usually
> recommended to use a vendor specific technology and avoid the large
> overhead of web services. For example, if you have a Microsoft windows
> form that needs to access Microsoft based business components on
> another computer, the recommended solution for connecting the two layer
> would probably be to use Microsoft .NET remoting. It will give you much
> better performance than web services while still allowing you to easily
> connect the two layers.
>
> Where web services really provide a great solution is when you are
> integration two systems/layers/applications that you don't have full
> control over or that don't share the same technology. In a case such as
> this your number one priority is getting the two systems to communicate
> properly and performance comes after that.
>
> So what you need to determine is what your requirements are and what
> problem you are trying to solve. Since you are trying to build a
> solution for you client, I would think that web services are your best
> solution. I would guess that the client is in control of their own
> technology and that you aren't free to dictate a proprietary
> technology such as DCOM or .NET remoting. The problem facing you seems
> to be and integration problem and not a performance problem. Unless
> there are other requirements that you haven't listed here (such as
> service level agreements outlining response times) I would recommend
> sticking with your web services based solution.
>
> Hope that helps
>
> Peter Kelcey
>


.

Relevant Pages

  • Re: Just tell me why ? so confuse...
    ... operations back the UI layer. ... > offer data analysis to my customer. ... >> It is true that web services can sometimes be the wrong technology to ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Just tell me why ? so confuse...
    ... offer data analysis to my customer. ... - the Web User Interface layer ... > It is true that web services can sometimes be the wrong technology to ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Just tell me why ? so confuse...
    ... It is true that web services can sometimes be the wrong technology to ... presentation layer through to business and data layers, ... if you have a Microsoft windows ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: interfacing with data layer
    ... This mechanism can sit between the Business layer ... If you have an "app server" that also hosts your data access code, ... have web services as the transport between web server and app (business ...
    (microsoft.public.dotnet.framework.aspnet)
  • BCS NOOPS - Autumn 2003 Programme
    ... "The Open Grid Services Architecture: ... "Generating Dynamic WWW Pages using PHP" ... ".NET Enterprise Web Services: ... Open Grid Services Architecture as the enabling technology for ...
    (comp.object)