3 ms·
Something that does help a little bit here is requiring clients to specify the fields that they need (as seen in GraphQL) rather than doing the equivalent of "s
by simonw 6y ago
Something that does help a little bit here is requiring clients to specify the fields that they need (as seen in GraphQL) rather than doing the equivalent of "select *" and giving them back everything.
This is useful because it lets you turn on detailed logging in order to understand exactly what fields are being used by which clients (identified by their API key or similar).
If you want to make a backwards compatibility breaking change like removing a field you now at least have a way forward: announce the field is going away, then watch your logs to see if it's still being used and who is using it. Then you can actively reach out to clients that use the deprecated feature and eventually make an informed decision about the overall impact when you finally remove it.