DotNet - Can you give an example of when it would be appropriate to use a web service as opposed to a non-ser

GeekInterview.com > Interview Questions > Microsoft > DotNet

Go To First | Previous Question | Next Question

DotNet | Question 59 of 165

Can you give an example of when it would be appropriate to use a web service as opposed to a non-serviced .NET component

Total Answers and Comments: 2

Last Update: May 09, 2008

Sponsored Links

Best Rated Answer

—

No best answer available. Please pick the good answer available or submit your answer.

August 30, 2005 08:18:53

Yaseen

RE: Can you give an example of when it would be appropriate to use a web service as opposed to a non-ser...

Webservice:

Appropriate when exposing the functionalitiss across differnt platforms(windows/Linux/Solaris..etc. ) or.NET to J2EE.

.NET Componet:

Appropriate when exposing the functionalitis within propritory O/S(.Net-.Net or Java-Java platform)

Is this answer useful? Yes | No

May 09, 2008 04:33:09

karthik palanichamy

Member Since: May 2008 Contribution: 3

RE: Can you give an example of when it would be appropriate to use a web service as opposed to a non-serviced .NET component

Communicating through a Firewall When building a distributed application with 100s/1000s of users spread over multiple locations there is always the problem of communicating between client and server because of firewalls and proxy servers. Exposing your middle tier components as Web Services and invoking the directly from a Windows UI is a very valid option. • Application Integration When integrating applications written in various languages and running on disparate systems. Or even applications running on the same platform that have been written by separate vendors. • Business-to-Business Integration This is an enabler for B2B intergtation which allows one to expose vital business processes to authorized supplier and customers. An example would be exposing electronic ordering and invoicing allowing customers to send you purchase orders and suppliers to send you invoices electronically. • Software Reuse This takes place at multiple levels. Code Reuse at the Source code level or binary componet-based resuse. The limiting factor here is that you can reuse the code but not the data behind it. Webservice overcome this limitation. A scenario could be when you are building an app that aggregates the functionality of serveral other Applicatons. Each of these functions could be performed by individual apps but there is value in perhaps combining the the multiple apps to present a unifiend view in a Portal or Intranet. • When not to use Web Services: Single machine Applicatons When the apps are running on the same machine and need to communicate with each other use a native API. You also have the options of using component technologies such as COM or .NET Componets as there is very little overhead. • Homogeneous Applications on a LAN If you have Win32 or Winforms apps that want to communicate to their server counterpart. It is much more efficient to use DCOM in the case of Win32 apps and .NET Remoting in the case of .NET Apps

Is this answer useful? Yes | No

Service Oriented Java Business Integration Review

Service Oriented Java Business Integration Review Introduction If you ve read through the texts which give you an introduction to SOA or Web Services you will often find them to be quite frustrating and the reason for this is because they spend too much time referencing business processes which are

Switched Multi Megabit Data Service (SMDS)

Switched Multi Megabit Data Service SMDS SMDS or Switched Multi Megabit Data Service is used to communicate on the Public Data Networks using the WAN networking technology The SMDS technology uses fiber or copper wires for networking There are many components in the SMDS networking environment that

Service Autonomy

Service Autonomy As Businesses continue to step up the process of constructing enterprise automation logic in the service format there is also an increasing need to step up both the efficiency and reliability that the services are intended to take on at run time This dire need is increased when it c

Service Oriented Infrastructure

Service Oriented Infrastructure Service Oriented Infrastructure is a systematic means for describing Information Technology infrastructures in the terms of a service The underlying principles of Service Oriented Infrastructure revert back to LDAP and Mainframe technologies among others Where Service

Service Reusability

Service Reusability One of the most vital principles of Service Oriented Architecture is that of service reusability And in today’ s day and age it can be said that we have been making a lot of progress towards improving both this central tenet and Service Oriented Architecture in general

Standardized Service Contract

Standardized Service Contract Standardized service contracts are one of the key Service Oriented Architecture principles They ensure that services that are in the same inventory of services are kept in compliance with contract design standards The services in a Service Oriented Architecture are able

Service Discoverability

Service Discoverability Service discovery protocols can be thought of as network protocols that allow for the automatic detection of both services and devices that are offered by a computer network’ s various devices There are a lot of service discovery protocols available In this article

Service Loose Coupling

Service Loose Coupling Loose coupling can be thought of as the resilient relationship that exists among two or more systems or companies that have some sort of relationship based on exchange Each transactional end should make its requirements explicit somehow and make very few if any assumptions abo

Service Encapsulation

Service Encapsulation What is Encapsulation In the realm of computer networking the term encapsulation is utilized to include data from an upper layer protocol in to a protocol on a lower layer Such a method of abstraction through networking allows many different layers to add on functionality and f

Service Composability

Service Composability The principle of Service Oriented Architecture known as Service Composability can be broken up into two basic principles Service Discoverability and Service Composition When it comes to the realm of Service Design a lot of attention is paid to the enabling of those characterist

Related Categories

—

User Name		Remember Me?
Password

Question Bank