locked
scalability in client object model vs web services RRS feed

  • Question

  • Hi all,



    I have a app in which I need to query a sharepoint site via services. The app will be under heavy usage so performance and scalability will be two of my priorities.



    I started to investigate which service approach is better and from a perf point of view it seems that client object model is the one officially suggested (http://msdn.microsoft.com/en-us/library/hh313619.aspx), but when I came to scalability I personally found that actually web services seem more potent than client object model. This is because it seems that web services have async support for IO bound operations (http://msdn.microsoft.com/en-us/library/cc646724.aspx) rather than client object model that doesn't (http://msdn.microsoft.com/en-us/library/ee857094(v=office.14).aspx#SP2010ClientOM_Asynchronous_Processing). I have to mention that I am using in my app C# 5 async/await feature in order to return the thread to the thread pool when queries are executed on the server.



    My question is, what should weight more in order to take a decision?

    Wednesday, July 24, 2013 1:52 PM

All replies