Just came across a very good article by Marc de Graauw over at InfoQ on why WS-RM is useless. His main point being that usually when you have reliable messaging requirements, they should be handled at the business logic layer rather than at the “transport layer”. I encountered some similar issues earlier this year when [...]
HATEOAS or “Hypermedia As The Engine Of Application State” is one of the core principles of REST and it essentially boils down to having links in the representations of your resources. How to apply this principle in the design of a service and the benefits that it provides depend on the nature of the service [...]
Over the past few years I’ve been helping a lot of government clients design and implement architectures for information-sharing. When it comes to information-sharing one of the most important aspects is the relationships in the data being shared because it’s those relationships that provide the context to help you understand and utilize the information better. [...]
Those of you who’ve worked on very large scale enterprise-wide architectures know that it’s always the people and politics that are the biggest hurdles. I came across the term “politecture” in Nick Malik’s blog here. You can follow the link for the definition, but it’s essentially an architecture that’s been designed with the influence of [...]
The RESTful approach is very attractive for large scale integration scenarios that cross many organizational boundaries. This is because the constraints imposed by the REST principles emphasize interoperability and scalability. The constraint of uniform interfaces supports those scenarios in which the consumer base for the services is so broad that it makes it difficult to [...]
The SOAP WS-* approach provides a broad set of standards and specifications for quality of service features and also gives developers a lot of flexibility to define custom interfaces for the services that they wish to expose. This flexibility is useful for application-to-application integration scenarios internal to an organization. This is also useful in scenarios [...]
