Hi , I am new to webservices, is there any example on the web where I could go to take a peek at an implementation of webservices being exposed through a servlet which calls a bean and returns values? Also, if you know of any worthy book on webservices please let me know. thanks
thanks guys. I will check out the book too. Axis looks very easy to implement compared to Sun's!
Joined: Jan 23, 2002
Originally posted by Pradeep Bhat: Are are any specific domains where Web Services are more likely to succeed? :roll:
B2B integration, for example. To generalize a bit further, web services is a good fit for situations where the two sides of an integration are not under mutual control and thus have to rely on standards as much as they can in order to preserve the business case for making the integration in the first place (it's probably not worth it if you need to re-implemented large parts of the partners' systems).
So, I'm trying to gain an idea here on Web Services. From what I interpret then, any integration between two disimilar systems can be performed as a web service? An example might be to get data from an ERP, and transform it using a product such as WebLogic Integration then pass it to another system, am I correct? Initially, I was under the assumption that web services were more like a middle tier layer in an n-tier architecture... maybe it is this too?
Just about anytime you need integration between two different platforms and high preformance (speed) is not critical, than Web services is an excellent option within the organization (A2A/EAI). That said, in just about any B2B problem where you are working with parterns outside your organization, web services makes sense because these types of intergations are (a) much more difficult with closely coupled systems like Java RMI or CORBA, and (b) integration with outside organization is usally not dependent on speed. Web services with SOAP are not super slow, like pain-pealing slow, but they are slower than something like Java RMI or CORBA IIOP because you can't achieve the same speeds parsing text as you can dealing with primitive values like ints, doubles, etc.
Building Scalable web services is much like building scalable servlets. If your web service is stateless, does not rely on things like singletons, and obeys the rules of J2EE in its implementation, then you should be able to scale it linearly with a simple ip-sprayer load balancer. Kyle
Originally posted by Pradeep Bhat: Any guidelines how to build scalable Web Services?
In the end, web services is only a way to expose services. The most important part in making a scalable web service would be the way that web service is implemented. In other words, the answer would be the same as for any other server-side software that needs to be accessed over the Web.