BackgroundIt’s all started when I encountered a strange behavior in one of the systems I work on.The system is a legacy system that uses a simple client server architecture implementing using web service – this was pre-WCF time so the options were only .NET remoting and web services. Now as part of major refactoring process of the system we decided to replace the communication layer from WS to WCF. The motivation is obvious: Alignment with Microsoft latest infrastructure.
performance improvement – http to TCP/ Binary encoding.
Easy maintenance.
Easy monitoring and configuration.
Extendible – interception points (behaviors).After the modification was completed I found that the system became slightly slower – how can it be.WCF performance vs. Web Service – What do we know This bring me to article from 2007 written by Microsoft: http://msdn.microsoft.com/en-us/library/bb310550.aspx“To summarize the results, WCF is 25%—50% faster than ASP.NET Web Services, and approximately 25% faster than .NET Remoting. Comparison with .NET Enterprise Service is load dependant, as in one case WCF is nearly 100% faster but in another scenario it is nearly 25% slower. For WSE 2.0/3.0 implementations, migrating them to WCF will obviously provide the most significant performance gains of almost 4x.” My BenchmarkStill articles are articles and facts are facts – “the costumer is always right” SmileIn addition in the article there was no mention of datasets specifically.In the legacy system we mostly use DataSet (I know pretty ugly but this is what we did in a legacy code what can I do…). Read more: Offir Shvartz
QR:
performance improvement – http to TCP/ Binary encoding.
Easy maintenance.
Easy monitoring and configuration.
Extendible – interception points (behaviors).After the modification was completed I found that the system became slightly slower – how can it be.WCF performance vs. Web Service – What do we know This bring me to article from 2007 written by Microsoft: http://msdn.microsoft.com/en-us/library/bb310550.aspx“To summarize the results, WCF is 25%—50% faster than ASP.NET Web Services, and approximately 25% faster than .NET Remoting. Comparison with .NET Enterprise Service is load dependant, as in one case WCF is nearly 100% faster but in another scenario it is nearly 25% slower. For WSE 2.0/3.0 implementations, migrating them to WCF will obviously provide the most significant performance gains of almost 4x.” My BenchmarkStill articles are articles and facts are facts – “the costumer is always right” SmileIn addition in the article there was no mention of datasets specifically.In the legacy system we mostly use DataSet (I know pretty ugly but this is what we did in a legacy code what can I do…). Read more: Offir Shvartz
QR:
Posts
0 comments:
Post a Comment