2020-04-09
2168
#graphql
Leonardo Losoviz
16731
Apr 9, 2020 â‹… 7 min read

Speeding up changes to the GraphQL schema

Leonardo Losoviz Freelance developer and writer, with an ongoing quest to integrate innovative paradigms into existing PHP frameworks, and unify all of them into a single mental model.

Recent posts:

tanstack table react table

A complete guide to TanStack Table (formerly React Table)

Discover how to use TanStack Table, formerly known as React Table, to build a table UI for a variety of use cases.

Paramanantham Harrison
Mar 28, 2025 â‹… 14 min read
javascript object prototypes

JavaScript prototypes: How objects inherit properties and methods

Explore what prototypes are, how the prototype chain works, and how to use the prototype chain to create inheritance between objects.

Ibadehin Mojeed
Mar 28, 2025 â‹… 7 min read
set up Node.js with TypeScript and Express

How to set up TypeScript with Node.js and Express

Set up TypeScript with Node.js and Express, focusing on configuring key elements for a smooth development experience.

Aman Mittal
Mar 28, 2025 â‹… 9 min read
featured image tsx extension

What is the difference between a .ts and .tsx file extension?

Examine the differences between the .ts and .tsx file types, their use cases, and best practices for a React TypeScript project.

Hussain Arif
Mar 27, 2025 â‹… 8 min read
View all posts

2 Replies to "Speeding up changes to the GraphQL schema"

  1. regarding discountedPrice example. I think create 2 different Product types instead of create 2 branches in discountedPrice in the same type is more clear to me. Because these 2 types of Products should belongs to 2 different Bounded Context(https://martinfowler.com/bliki/BoundedContext.html). As time goes on, the 2 branches will grow. It won’t look as simple as it was created at the beginning. And there will be more fields like discountedPrice in the Product type. The logic will be more verbose and might need to be decoupled. So I don’t think using the same discountedPrice to handle the requirements of tutorial team and workshop team is a good idea. Though this is a great post!

  2. Actually, i prefer multiple graphql layers to handle the issues in this post. there will be 2 graphql layers in companywide . the first layer just combine different data sources including: DB, RESTFul, etc. but don’t do any modification. the 2nd layer built on the 1st layer which is a BFF(https://www.infoq.com/presentations/graphql-bff/) layer which only service those front-ends.

Leave a Reply