The document discusses agile schema development, which involves shipping changes daily, focusing on client needs, and guaranteeing compatibility. It recommends maintaining a single graph and optimizing as needed. Key aspects include scoping changes to current requirements, maximizing reuse, validating changes, deprecating fields with reasoning, and isolating and testing legacy fields.

1. Agile Schema Development
Evans Hauser
Platform Developer, Apollo

2. Platform Developer
@evanshauser

3. Developer velocity 💪

4. 1 Ship every day
Focus on client needs
Guarantee compatibility
Agile Schema Development
2
3

5. Demo time!

6. “Schema validation at PR commit is a
game changer. We've already detected and
prevented a number of schema changes
that would have led to weeklong service
outages for our native app customers.”
Dan Boerner
Distinguished Product Manager at Expedia Group
apollographql.com/customers/expediagroup

7. Ship every day
Focus on client needs
Guarantee compatibility
Agile Schema Development
1
2
3

8. ● Maintain a single graph
● Optimize as needed
● Enable requirement changes
Ship
every day
1

9. ● Scope to current requirements
● Maximize reuse across clients
● Write schema documentation
Focus on
client needs
2

10. Guarantee
compatibility
● Validate changes with usage
● Deprecate with reasoning
● Isolate and test legacy fields
3

11. Ship every day
Focus on client needs
Guarantee compatibility
Agile Schema Development
1
2
3

12. Schema validation docs
bit.ly/schema-validation
principledgraphql.com
Connect with me(@evanshauser)
What’s next?
1
2
3

13. Deprecate with kindness
Delete with care