Our discussion on the $resource
service should start with understanding why we require $resource
. The $http
service seems to be capable of performing all types of server interactions. Why is this abstraction required and against what type of system does the $resource
service work?
To answer all these questions, we have to introduce a new breed of service (server side, not Angular services): RESTful services.
"There is an API for that!"
Apple did not coin this, but this indeed is a reality now. There is an API for everything. Almost all of the public and private services (Google, Facebook, Twitter, and so on) out there have an API. And if the API works over HTTP, there is a pretty good chance that the API is RESTful in nature. We don't have to look far; MongoLab too has a RESTful API interface and we have used it!
Representational State Transfer (REST) is an architectural style that defines the components of a system as resources. Actions...