-
Type:
Task
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: backend, documentation
-
2
-
S
With many of our APIs becoming public, we should investigate how to approach their backwards compatibility going forward. One option could be versioning our endpoints, another could be flexible approach to the payload. There are probably many alternatives, hence the requirement for a spike. The desired outcome could be an evaluation of possible options, from which we can commit to a decision for implementation going forward as this becomes more of an issue.
Justification:
Having a strategy on API compatibility allows us to offer stronger guarantees to our customers, the consumers of our APIs