[英]How to organize web services, so developers can easily find them?
We're developping a software for a large bank. 我们正在为一家大型银行开发软件。 So, the problem is that bank operates in SOA way. 因此,问题在于银行以SOA方式运作。 I mean, we have an entry point to the system and then there are WebServices fow everything, and when I tell everything, I mean EVERYTHING, there are like 3500 services. 我的意思是,我们有一个进入系统的入口,然后有WebServices可以访问所有内容,当我告诉所有内容时,我的意思是所有内容都包含3500个服务。
Right now these services are just stored in a database table with (or without, sometimes) their descriptions, so, you can imagine the hell we're living in. I guess that sometime it's easier to implement new web service than to find the right one, this produces redundancy. 现在,这些服务只是存储在带有(或没有,有时没有)描述的数据库表中,因此,您可以想象我们生活的地狱。我想有时候实现新的Web服务比找到正确的服务更容易。第一,这产生了冗余。
So, my question is, is there some way of organizing this kind of stuff? 所以,我的问题是,是否有某种方式来组织这种东西? I mean, we have many bussiness lines and some common components, but I'm totally newbie in WS. 我的意思是,我们有很多业务专线和一些通用组件,但是我在WS中完全是新手。 Anyway, I need some kind of way to provide the developers with information what service they can use in any case. 无论如何,我需要某种方式为开发人员提供信息,使他们可以在任何情况下使用什么服务。
A good documentation may help. 好的文档可能会有所帮助。 Or google for the more sophisticated approaches like web service registries using WS-Inspection or UDDI. 或用google搜索更复杂的方法,例如使用WS-Inspection或UDDI的Web服务注册表。
I've seen it done with a simple web site where developers can find descriptions, WSDLs, etc. I think it's sufficient; 我已经看到它是通过一个简单的网站完成的,开发人员可以在该网站上找到描述,WSDL等。 I wouldn't recommend UDDI or buying a sophisticated tool. 我不建议使用UDDI或购买复杂的工具。 Yours is a problem in advertising and marketing. 您的广告和营销存在问题。
High Level Logic: Rethinking Software Reuse in the 21st Century 高级逻辑:重新思考21世纪的软件重用
http://highlevellogic.blogspot.com/2010/09/high-level-logic-rethinking-software.html http://highlevellogic.blogspot.com/2010/09/high-level-logic-rethinking-software.html
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.