Archive for the ‘architecture’ Category

Two Perspectives on HATEOAS


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 [...]

No Comments

Service Reuse


The more I think about the phrase “service reuse” or any other variation of it, the more I don’t like it. I feel like it’s making me think about services from a perspective that is too technical and too low-level. Reuse is something you want to achieve with code but you shouldn’t be thinking about [...]

(1) Comment

Extending Reuse to the Last Mile


While services make it easier to share your data and functionality, some developer still has to write the code to consume your service and present the results to the end user. In many cases, that code to consume and present a visualization of the service can be reused by other applications. This has already exploded [...]

No Comments

SOAP/WS-* vs. REST and The Art of Politecture


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 [...]

No Comments