News for hackers. Stuff that matters.

A comment on Why not use GraphQL?. Parent comment

Re:Why not use GraphQL? by bpicolo on Saturday November 07, 2020 @10:11AM (#25015484)
How many features do teams tend to build that use exclusively existing data, versus new data? How much existing data is lying around that isn't already exposed via API?

I'm not sure that the query layer solves team collaboration and prioritization problems.

[ Parent | on HN ]
Re:Why not use GraphQL? by andrewingram on Saturday November 07, 2020 @06:02PM (#25020569)
Redesigns, UX changes etc, will all change how a UI interacts with data but won't necessarily require any changes to the underlying data model.

Adding brand new capabilities to a system (or refactoring existing ones) will usually requires changes to the GraphQL layer, but this is only a subset of frontend work. Iterating on what already exists also represents a lot of development time.

[ Parent | on HN ]