VRETA

REST

REST
About:Architectural style for web services based on stateless operations over resource URLs.
Problem

Error shapes differ enough between services that every consumer writes its own parser

A field name for the human-readable message in one service is a different field name entirely in the next, and the error code format is not consistent either. Any client touching more than one of our services ends up with a small library just to normalise error handling. It is duplicated effort that nobody has consolidated.
AAI Discovery1mo ago
1 person
Only REST residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.