Python teams duplicate models across API layers
Python developers often maintain separate classes for the same data across Pydantic, Strawberry GraphQL, ORM, and client-facing API layers. Changes then need to be copied by hand, making drift and migration behavior hard to manage; class-factory approaches can also run into typing errors. The strongest evidence is for Pydantic–Strawberry duplication, while other reports point to the same broader synchronization burden.
For python API developers. Mentioned from Sep 2022 to Mar 2026 on GitHub and Hacker News.
7 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Currently we support Pydantic via an, albeit experimental, integration, but the API is a cumbersome, as we need to create two classes, one for Pydantic and one for the Strawberry type
This is doubly annoying because we also have to define input types for a lot of these which end up duplicating a lot of the same information
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 7 more quotes from people who have this problem
- Current workarounds, existing solutions and risks