Standard components for db tier + thoughts

I have started a project at my company, in which I will find the most suited component to use for all db access for all applications in my company. We use 95 % oracle, but some sql server applications will also be developed.

Right now we are using a dbcomponent which is only accessible via webservice calls. I dont think that is a good solution. What if 50 or 100 apps call that component every time they need to make a call to get something from the database. That is a lot of xml stuff flowing through the network. Anyway , I don't like it, what do you think?

My thought is to install the component on our application servers (we have 4) and then use webservices to feed the webb apps and winforms apps we develop. That still means a lot of traffic and a lot of webservice calls, but they exchange valid and structured information, that is the information needed to feed the presentation layer. All communication between the dblayer and the business layer takes place on the server, without webservices.


What do you think about that architecture? Will it hold? Is it good practice?

My problem is that I have people here who think webservices are the key to everything. They are very happy with the way they do it now, using webservices to communicate with the dbcomponent. But I think it is a bad idea, what do you others think?????? I think webservices should only be used to provide valid information.




And my second issue, which component should we use? I reallyl like microsofts component in their application block. Sadly it only exist for sql server. Has anyone rewritten it for oracle? Are there other specific oracle data application blocks??


please let me know your thoughts... I know there are lot of gurus and architectural experts here

Henrik