Content
@
0 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
Am I wrong for thinking GraphQL is how builds APIs today? GraphQL as core (anyone can select just the data they need) Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL) and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like What am I missing / where does this go wrong? trying to open my mind on GraphQL https://gist.github.com/tim-smart/e10e4cbaeff35242d8352adead30bef9
7 replies
4 recasts
41 reactions
Arti Villa
@artivilla.eth
It's easy to start with but hard to master. Issues at scale are hard to debug. So if you're just building a single client vs multi clients, its not really needed. right tool for the right job. If you're using typescript, https://drizzle.com just works, works with any db, AI can write your boiler rest api and I'm sure there are tools to automate. And it kills on performance. I hate cli db management and they have the perfect solution for me. https://orm.drizzle.team/drizzle-studio/overview I went from never touching backend to building full stack with typesafety (zod) in a day. It's also a thin wrapper so it won't stop you from doing things low level. which a reason to not want a lot of abstractions. I literally change prod db code via an editor. Can't get better than that.
1 reply
0 recast
6 reactions
Samuel ツ
@samuellhuber.eth
@rafi @nastya any idea on Zod + drizzle v Effect SQL ?
2 replies
0 recast
1 reaction
Rafi
@rafi
I’d with Drizzle and write necessary wrappers either Effect.tryPromsie when integrating it into Effect runtime to avoid hardcore vendor lock in. Plus, it makes scripting and throw-away coding easier
0 reply
0 recast
0 reaction
