4 ms·

/orders /orders2 /orders3 /orders4 /neworders /getordersbutonlythistype

• earthboundkid 5y ago
  If you're changing the endpoint that same amount but keeping the URL, you've just imposed a ton of churn on everyone downstream. It's a tradeoff, like everything. Try to get the API right the first time. Try to avoid introducing new APIs. Try to avoid breaking the old API. There's no silver bullet.
  • ebiester 5y ago
    After all, your business never changes and neither do the constraints.
    • earthboundkid 5y ago
      Who are you arguing with?
• underwater 5y ago
  And /orders uses an old data layer in a way that is incompatible with the new one, so the team can't deprecate the internal DB abstractions. And they can't introduce a new caching layer without making it work across the new and old abstractions. Etc, etc.