Create robust and maintainable projects using the right tools
Damn, didn't know they were re-writing core elements of pydantic in rust.
P.S. I'm not sure you've covered GraphQL in python before. I'm sure you'll love using strawberry-graphql the most. I'd love your thoughts on that!
Hi Srikanth, yeah I never got into GrahQL because I'm not a huge fan :)
I found it complex and not relevant for my activity, but strawberry-graphql seems to be a great library from what I saw.
GraphQL definitely adds an unnecessary layer of complexity for small projects.
But, I think it forces you to think about the User data structure. Instead of keeping things willy nilly.
I think the complexity helps address long term issues of mainting a million api routes.
May be you are right, but GraphQL also adds its own challenges regarding caching, pagination, error displaying, etc... You should be sure of the tradeoff you want to accept.
Maybe consider writing an article about it. I'd love to know what traps I shouldn't fall in.
I kind of skipped basic REST apis. And started out with GraphQL. So I'd love to know.
So far, anytime I have faced challenges the strawberry community is able to guide me through it, to a certain extent.
Yeah, may be I will do that one day, but I need first to battle test GraphQL to be sure to argument what I will write 😆
Damn, didn't know they were re-writing core elements of pydantic in rust.
P.S. I'm not sure you've covered GraphQL in python before. I'm sure you'll love using strawberry-graphql the most. I'd love your thoughts on that!
Hi Srikanth, yeah I never got into GrahQL because I'm not a huge fan :)
I found it complex and not relevant for my activity, but strawberry-graphql seems to be a great library from what I saw.
GraphQL definitely adds an unnecessary layer of complexity for small projects.
But, I think it forces you to think about the User data structure. Instead of keeping things willy nilly.
I think the complexity helps address long term issues of mainting a million api routes.
May be you are right, but GraphQL also adds its own challenges regarding caching, pagination, error displaying, etc... You should be sure of the tradeoff you want to accept.
Maybe consider writing an article about it. I'd love to know what traps I shouldn't fall in.
I kind of skipped basic REST apis. And started out with GraphQL. So I'd love to know.
So far, anytime I have faced challenges the strawberry community is able to guide me through it, to a certain extent.
Yeah, may be I will do that one day, but I need first to battle test GraphQL to be sure to argument what I will write 😆