text: Survival of the simplest Evolution Platform Developer Build (Build: 5.6.50428.7875)2004-02-20T22:23:00ZTCP/UDP?<p>With all the WS* messaging protocols , especially <a onmousedown="return clk(this,'res',3)" href=""><font color="#0000cc"><b>WS</b>-<b>ReliableMessaging</b> </font></a> it appears that they have moved the *TCP* like features/behavior higher up in the layers .Do we still need to TCP lower in the transport layer , Will UDP make a comeback?</p> <p> </p><div style="clear:both;"></div><img src="" width="1" height="1">NeerajSr OS<p>Recently finished working on another customer issue where an application working for a few years suddenly started failing. It was an update they recently made which broke their app.<br />This got me thinking about the current state and future of software development.<br />In this respect the current trend towards SOA looks especially important; the services based development lets you reuse code without letting that code pollute your space. This lets the service control their environment.<br />However , there could be more than one service running on a machine and an update to some other service could effect another one ,bringing us back to the same problem , even with this though your exposure is still reduced however ,it is not enough.<?xml:namespace prefix = o<o:p></o:p></p> <p.<o:p></o:p></p> <p...<br />By controlling the number of applications that run on the device we reduce our efforts in testing , make locking it down easier and just reduce the exposure to a large extent.</p> <p>[These postings are provided "AS IS" with no warranties, and confer no rights.This site represents my views only and not the views of my employer.]</p><div style="clear:both;"></div><img src="" width="1" height="1">NeerajSr over UDP<p><a href=""></a></p> <p>Saw this coming out recently, i have been wondering why no such spec was available for a long time . With all the reliablilty and other features being built in at the application level Soap over UDP should be a very viable option.<br />i strongly feel UDP is going to stage a comeback , richness epecially with the multicast option that it brings will find a lot of use</p><div style="clear:both;"></div><img src="" width="1" height="1">NeerajSr on SOA<P>Some of fellow bloggers pointed out the following post on <A href="">zapthink</A> .Some of the situations this article points out IMHO, are not applicable or non-existent .</P> <P>1) homogeneous environment : In a real world enterprise you will never know if you have such an environment , as the leadership changes the technology a company adopts changes , an application you are writing today for a homogeneous environment may not be operating in one , a year down the line or even 6 months down the line .Moreover isn't it one the goals of SOA is to be able to write application which can evolve/adapt to changing environment so environment should not matter.</P> <P>2) Real time performance is critical . This may be applicable in the present scenario while we are still working on the infrastructure and tools to enable SOA , but few years down the line will this be applicable? Recently in one of interviews on <A href="">theserverside.net</A> Don Box talks about taking the SOA model down to the level of in process / cross process communication . As we invest more into the protocol and network stack things will be better . SOA is more of a paradigm and its the implementation that will make real time “enabled”.</P> <P>I have seen some “SOA” based architecture designs , i think the challenge here is to how to factor SOA in a design . How to make a distinction as what needs to be service and what needs to be component. What are the boundaries where messages are exchanged and where method calls made. With the current infrastructure that is available for developers this clarity is important . As implementations become better this may become less imperative.</P> <P><FONT face=Arial color=#000080 size=2>This posting is posted “as is” and guarantees no warranties and confers no rights</FONT></P><div style="clear:both;"></div><img src="" width="1" height="1">NeerajSr