My understanding is that REST imposes a bunch of restrictions about how an API is suppose to work.
For example the idea that you can just communicate a single base URL and document formats, and other urls are deduced from that. Which add complexity, but make the system more able to evolve.
My thinking is that these constraints are inappropriate for an internal API, where you could embed knowledge of how to construct a number of URL's in clients.
Also some tools, like .NET, have good support for mapping XML schema's to classes, and I don't know of equivalents for JSON.
For example the idea that you can just communicate a single base URL and document formats, and other urls are deduced from that. Which add complexity, but make the system more able to evolve.
My thinking is that these constraints are inappropriate for an internal API, where you could embed knowledge of how to construct a number of URL's in clients.
Also some tools, like .NET, have good support for mapping XML schema's to classes, and I don't know of equivalents for JSON.