Microsoft often delivers excellent development tools like VS and many others to easily and rapidly create all kinds of aplications. It won't take us very long to build a working ASMX and see the incredible result with what WSDL can do for us. This is a big ++ for all of those who plan or are forced to get into the SOA arena which Microsoft and many software leaders like IBM and others are throwing at us right now. Do be extremely cautious because the evil is in the detail and it can burns you really bad if it's not done right. Here is a very interesting article that definitely offer lots of excellent ideas to start; http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/SOADesign.asp
Have fun
Thanh wrote:This is a big ++ for all of those who plan or are forced to get into the SOA arena ...
I don't think there is anyone forcing anybody. You use based on your needs.
Firedancer wrote: Thanh wrote:This is a big ++ for all of those who plan or are forced to get into the SOA arena ... I don't think there is anyone forcing anybody. You use based on your needs.
"Forced" certainly sounds very forceful. Unfortunately, there are people out there who bought into this SOA model and strongly believe it's the way to go without really and fully understand the limitation and consequence of it. All they see is the hype and benefits it brings to the table. I have no doubt as the SOA space continues to improve, it will offer more reasons to take the central stage of the distributed arena. Windows Communication Foundation formerly known as Indigo seems to fill that space quite well.
I read that article again last night and have another comment about one of the anti-pattern that many people jump into the web service bandwagon may fall into the trap. The code looks like this
<WebMethod()> _Public Function QueryDatabase( ByVal Database as String, SQLQuery as string) As DataSet
Every .NET developer visit MSDN and see DataSet being promoted aggresively as the data carrier. Now they turn around and tell us not to use it in this way. Again, I'm being critical and don't understand why can't they serialize it into an xml schema so that the NON .NET service consumers can understand it.
Thanh wrote:Every .NET developer visit MSDN and see DataSet being promoted aggresively as the data carrier. Now they turn around and tell us not to use it in this way. Again, I'm being critical and don't understand why can't they serialize it into an xml schema so that the NON .NET service consumers can understand it.
choongseng wrote: Thanh wrote: Every .NET developer visit MSDN and see DataSet being promoted aggresively as the data carrier. Now they turn around and tell us not to use it in this way. Again, I'm being critical and don't understand why can't they serialize it into an xml schema so that the NON .NET service consumers can understand it. I think it serialized in to XML when the Dataset is being sent over on the wire. Just that the format is MS propriety, but not cross platform standard. Isn't it?
Thanh wrote: Every .NET developer visit MSDN and see DataSet being promoted aggresively as the data carrier. Now they turn around and tell us not to use it in this way. Again, I'm being critical and don't understand why can't they serialize it into an xml schema so that the NON .NET service consumers can understand it.
That's also my understanding at the moment.