With the popularity of grpc and thrift I've not seen many cases where REST is needed for internal communication. I understand it's required for external communication though. Grpc and thrift are kind of the opposite direction APIs are taking (or have already taken) as in don't we hate RPCs? We do but speed and efficiency are much more important for internal comm (and binary protocols are just one of the factors at play here).
Yeah, it's designed for discoverable APIs on the open internet, why use it for internal communication I have no idea. All the time I've wasted making apps slower and worse, and arguing over it, just because it's the "correct" RESTful way, and creating and maintaining documentation, when there's only one single client, and it's also managed in the same team. It just becomes a line drawn in the code in a random place where everything becomes more difficult, dogmatic and impractical.
