<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8907963\x26blogName\x3dWS-Comments\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://ws-comments.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://ws-comments.blogspot.com/\x26vt\x3d-792153501087690591', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

WS-Comments

perspectives on open-source and web services

Friday, April 01, 2005

visa does a lot of transactions

proof.

when I first started reading, I thought it would be insane if those thousands of transactions per second were web services transactions, because those would be some pretty fat message stacks and I wouldn't even want to imagine the infrastructure required to keep them going at that pace.

in any case, the dispute-resolution scenario seems very conducive to a web services approach. and it made me think of the WS standards in a different perspective - outsourcing. essentially, Visa, member banks, and everyone else that uses the various WS standards is outsourcing the development of their internet-capable communication infrastructure.

I thought of it this way...

without WS standards, if Visa were to accomplish the same thing, they would need to spend time and money developing a method by which all of their member banks could communicate, via the internet, to their backend system for the dispute-resolution process. however, with WS standards, they can settle on the publicly-available HTTP, SOAP, REST, FTP, etc standards.

the article did not go so far as to say whether or not they were using things like BPEL4WS to model/manage the business processes involved in the entire procedure of dispute-resolution, but if they do, then that is yet another methodoly/platform that they did not have to develop in-house.

obviously, for those companies that pay to help develop these standards, it's not entirely free. however, it does help the standards-developers stay focused on their standards, rather than having to worry about this or that implementation of the standard.

that is all for now, though I'm still reading a few more articles, so another post may yet happen.

0 Comments:

Post a Comment

<< Home