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:

Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Discover how to use Gemini CLI, Google’s new open-source AI agent that brings Gemini directly to your terminal.

Chizaram Ken
Jul 10, 2025 â‹… 8 min read
React & TypeScript: 10 Patterns For Writing Better Code

React & TypeScript: 10 patterns for writing better code

This article explores several proven patterns for writing safer, cleaner, and more readable code in React and TypeScript.

Peter Aideloje
Jul 10, 2025 â‹… 11 min read
A Guide To Wrapper Vs. Container Classes In CSS

A guide to wrapper vs. container classes in CSS

A breakdown of the wrapper and container CSS classes, how they’re used in real-world code, and when it makes sense to use one over the other.

Temitope Oyedele
Jul 7, 2025 â‹… 10 min read
Stagehand and Gemini logos on a gradient background symbolizing AI web automation

How to build a web-based AI agent with Stagehand and Gemini

This guide walks you through creating a web UI for an AI agent that browses, clicks, and extracts info from websites powered by Stagehand and Gemini.

Elijah Asaolu
Jul 4, 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