Seemingly-Consistent Services Architecture

Mostly refers to RESTful services. One of the selling points of RESTful services architecture is the fact that it offers a consistent approach about how response codes are handled. Although the thruth is it is not the same developer who writes all your services in your organization. For example, attribute "someid" could be a request parameter for your services, but a path parameter for some upstream service. A path parameter looks something like this:

/service/someid/{someid-value}

So what would be a "400" error code in your service, is a "404" for the upstream service. So a simple pass-through of error codes is not possible - so much for consistency.