4 ms·
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 slowe
by jseban 5y ago
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.
- DeathArrow 5y ago>why use it for internal communication I have no idea Here are a few potential reasons: 1. HTTP is familiar 2. RESTful seems easy 3. people are told that RESTful is the way to go, is cool is mainstream and is modern