Send proper Response Status

Most of the consuming services will be implemented according to the Status codes that we provide, and hence we must always provide the most appropriate HTTP Status codes in our response. It will be meaningless if we send a 200 (Status: OK) for a service where the resource is not found or even 500 (Server error) where there is actually a NullPointerException.

Note: More details on HTTP methods and status codes can be found here.