A well-designed REST API doesn't merely expose each DB table


A well-designed REST API doesn't merely expose each DB table.

Doing so leads to:
🚫 Many HTTP calls
🚫 Returning data the UI doesn't need
🚫 A lot of client-side code to reformat responses.

Instead, carefully consider what data the consumers need, and how they will use it.

View original on X