wood burning stoves 2.0*
The moose likes Web Services and the fly likes Are web services for B2B alone? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Are web services for B2B alone?" Watch "Are web services for B2B alone?" New topic
Author

Are web services for B2B alone?

Faisal Khan
Ranch Hand

Joined: Jun 29, 2003
Posts: 285
I have never had the opportunity to work with web services but find the technology very intriguing. Are web services of really worth when it comes to B2B or do other situations call for its practical usage?


The secret to creativity is knowing how to hide your sources.
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Not just B2B but also B2C and even C2C. The key is that the communicating parties are independent of each other. What I mean is that if the implementation of one side can be dictated by the other, the universal interoperability of web services protocols doesn't have that much value anymore. However, if performance is not the most important factor, web services are a solid option in those cases as well.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
Actually, we find the largest market for Web services to be in internal application integration. Most companies have both MS and Java technologies deployed internally, and being able to allow these two types of applications to talk to each other is immensely valuable.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Well, if you've got a bunch of "legacy" that you don't want to migrate, I guess that still counts as "not being able to dictate the other side". Also, if there's a foreseeable need to switch platforms, going web services is a safe move even though you would have the possibility to have every integrating system running on the same platform today.
Faisal Khan
Ranch Hand

Joined: Jun 29, 2003
Posts: 285
Thanks guys.
My questioning was in view to what Kyle brought forth. There was a recent discussion in our company about whether to give web based front end to in-house users or desing a new VB system.
I proposed making use of web services and leaving all the business logic in Java and then have a VB front end using the Java web services.
Just wanted to check whether that was an appropriate usage.
Stefan Sorman
Greenhorn

Joined: Dec 04, 2003
Posts: 2
Using web services is probably an ideal way to publish the interfaces of existing components in a company that produces software on a regular basis. It is a way to make results available from previous projects which improves quality and reduces development time. The approach shows great promise.
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
Originally posted by Faisal Khan:
Thanks guys.
My questioning was in view to what Kyle brought forth. There was a recent discussion in our company about whether to give web based front end to in-house users or desing a new VB system.
I proposed making use of web services and leaving all the business logic in Java and then have a VB front end using the Java web services.
Just wanted to check whether that was an appropriate usage.


It certainly sounds appropriate to me.
Kyle
Paul Monday
Author
Ranch Hand

Joined: Aug 28, 2003
Posts: 41
I have to agree, people shouldn't lock Web Services into B2B scenarios. The "need" for service-oriented architectures go well beyond B2B. In most cases the need is along the lines of "integration", "future proofing", "opening up interfaces", etc...
These tasks apply to just about every part of the computing industry (b2b, storage management apps, integration paradigms, etc...).
In all cases, being pragmattic about the application and expectations from Web Services is a good idea though...they are not a magic bullet for all problems...just because you produce a web service doesn't mean everyone will want to use your web service...that's where standards and pragmattic interface planning come into play.


Paul B. Monday<br />Author, Web Service Patterns: Java Edition
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Are web services for B2B alone?
 
Similar Threads
What is UDDI
.Net And J2EE Interoperability
Web Services Survey
Web Services Survey
Webservices and J2EE