The article Roots of the REST/SOAP Debate (along with many others like it) claims that SOAP web services have a limitation in that resources they work with are not directly addressable via a URI, but that you have to connect to the SOAP endpoint and then call a method on it. The analogy used is as follows...
Databases cause two performance problems for applications. Firstly they are difficult to scale out compared to other server roles which means they can easily become the scalability bottleneck, and secondly they are on a remote machine which means that each query made to them involves network latency...
On every database-backed project I've worked on, which is quite a few ranging from 4 to over 50 developers, the number of people working on the database is relatively small. Typically in a three-tier application the ratio of developers on UI:services:data is around 5:2:1 because high quality user...
There seem to be a lot of blog entries at the moment arguing over the relative merits of XML, JSON, YAML, S-Expressions, etc. as a data interchange format, and Web Services, WS-* Services and REST-style as the application protocol implementation. But while various articles make interesting academic points...
In the last entry we created a service container that could construct a hierarchy of singleton services from configuration, which could pass services as objects, lists or dictionaries as constructor parameters to other services. This time we'll refactor the code to allow arbitrary types of argument...
In the last entry we created a service container that could construct a hierarchy of singleton services from configuration, which passed services as constructor parameters to other services. This time we'll extend the container to allow more complex parameter types such as lists or dictionaries of...
In the first entry in this series I outlined why it might be better to write your own service container rather than use an off-the-shelf one, and wrote the configuration classes and shell for our initial version of a service container that can load a hierarchy of dependent services. In this entry I'll...
In my last entry I described how to extend the ASP.NET cache to allow it to be hosted out-of-process as a distributed cache , and it turned out that the hardest part of it would be to change your existing code to use it rather than the in-process cache if you weren't using a configurable service...