Web Service for Bank's internal operations
Dear All.
I am very new to XML Web Services. I read that ther are suitable for connecting different organizations and different systems.
But What do you think? Is it true logic to use Web Services for inside bank operations:
f.e: AddNewCustomer, EditCustomer, DebetAccount. So, in general operatiosn that use "Data Manipulation Language". So, not to use siply Client-Server architecture, there will Client-WebSrvice/s - Database Server.
As we know bank's has bunch of records. Are WebServices good candidate for such bunch operations?
Thanks in advance.
Teymur
When you look at performance, I think it will probably work, if the webservices are designed right. You should be aware of some requirements:
- Does the client need to wait for the transaction in the database to complete, or can this happen a-sync?
- How many connections are going to be made at the same time?
- Is the database a single database-cluster or is this done trough the webservices?
Another very important notice in this case is security. Standard webservices run at the http port and messages are sent in plain text. How are you going to make shure the messages are authentic and authorized?
Thank you for your reply.
But you know, I have not ready or working environment. I simply need comparison of using webservices or client-server architecture in order to developer banking software. I am in planning step. That is why I need real-word proven why or not why? What can I benefeit from web services if I use it? Or what disadvantages there? Or may be, you can say "if so, use application server instead of webserver (because of webservices)".
Please, help me in order to choos the best architecture.
And what about connections. I heard that connection pooling feature of webservices is one of the greatest feature.
Thanks in advance.
Teymur
Hmmm... you can create a web service deployed in a web server and you can there apply connection pooling through ADO.NET 2.0, for instance. But being rigorous, web services don't include db pooling capabilities
Web services are all about a communication mechanism through well established standards like HTTP, TCP, XML, SOAP and a new set of protocols known as WS-* specs
Compared with the traditional C/S architecture looks better because in a C/S architecture every client must establish a direct connection with the database so you may waste lots of resources
As I told you before, Web services per-se won't solve your life but at least enable you to centralize in a web server some common activities. Not just the connection pool we talked before but also data caching, among other benefits
While you gain benefits in the execution space, you pay in a little additional complexity in development and maintenance one
Hope it helps
Hi,
let me give you basic funda of web services which will help in your decision.
Web service is a way of designing solutions for two requirements :
1. Interoperability - where u need to integrate systems on different platforms like mainframes, unix , windows , j2ee or .net
2. Loosely coupled integration : when systems from different organizations need to be integrated.
If you have these requirements go for WS .. else NO.
http://DotNetWithMe.blogspot.com
vikas goyal
Thanks for your reply. But I need not to directly connection to DB. I need something in the middle layer acted with some features of webserver. Connection Pooling, caching etc. In general, what I have to use in .NET world which can act as application server? Note, that I am going to develop software for bank's internal operations. I mean there will be bunc of DML operations and plus more than 10 branches. But Client will use C# WindowsForms.
Thanks in advance.
Teymur
Hi All,
I have the same problem and just wandering how to implent 3 tier in this case?
Need web service or remoting or other simple ways?
Thanks.
Jannet
Check this url
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdadotnetarch13.asp?frame=true
If your looking for banking applicaiton try to see the security aspect.
Use sql procedure instead of DML.
Plus there are many other aspect which you need to take care of.
The biggest downfall in the banking applicaiton are that you cant transact in normal soap protocol due to sniffing problem.
You should use remoting and that also binary remoting format.
It is the fastest you have got plus add a layer of security and you will see the difference.
Send encrypted signed data or send data packaged as a bin packet which cant be read on network.
You can then use web haversting technique to control the no of record and optimization issues.
Lot of these performance issue have been taken care of in the new WCF (.net 3.0) architecture and I recommend using that if possible along with use of strict algorithm use (symmetric) if possible.
