Last active
October 7, 2023 14:15
-
-
Save WolfEYc/1b6aa53f5dd341131d895927edf8bc6f to your computer and use it in GitHub Desktop.
Apollo gql goodies
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Design your schema based on how data is used, not based on how it's stored. | |
2. FE devs have more freedom to pick and choose what fields they want, | |
instead of being stuck to the fields of the Rest API | |
and wait for a data engineer to update or create Yet Another™ endpoint. | |
3. FE devs can rename fields to what they want to consume it as on the FE in their request, | |
instead of having to manually parse and rename the json response. | |
4. Data Engineers will spend less time changing or adding queries over the same data, | |
and will be able to instead provide a singular interface over the same data, | |
which can be consumed more flexibly by FE devs. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment