[deleted]
Prisma – Database tools for modern application development
11–20 of 88 posts
Re: Prisma – Database tools for modern application development
#12is this different from any other ORM library?
Re: Prisma – Database tools for modern application development
#13Forgive me the obvious elephant in the room - where is Swift and Java/Kotlin support?
Re: Prisma – Database tools for modern application development
#14It's been interesting watching Prisma, formerly Graphcool, transition from backend-as-a-service to open source backend to client ORM library. They also use bleeding edge patterns, so I always know where to go for examples as stuff gets adopted mainstream :) Keep up the good work Prisma team! Question specific to this autogenerated client: does that mean I have to bump client version numbers every time my backend sche…
> They also use bleeding edge patterns, so I always know where to go for examples as stuff gets adopted mainstream :)
Do you have specific examples of cutting edge patterns they use that you can share? I'm always interested in seeing concrete examples of (often) abstract patterns/concepts.
Re: Prisma – Database tools for modern application development
#15Massively simplifies working with data and databases cos they don't use ORM.
Re: Prisma – Database tools for modern application development
#16This is amazing! What about Python?
Between SQLalchemy, Django, Peewee, and quite a few others, Python is fairly well-covered by ORMs already.
Re: Prisma – Database tools for modern application development
#17Re: Prisma – Database tools for modern application development
#18It's been interesting watching Prisma, formerly Graphcool, transition from backend-as-a-service to open source backend to client ORM library. They also use bleeding edge patterns, so I always know where to go for examples as stuff gets adopted mainstream :) Keep up the good work Prisma team! Question specific to this autogenerated client: does that mean I have to bump client version numbers every time my backend sche…
You've hit a GraphQL specific issue with APIs. Generally I think the best practice is to only make additive changes to your API and deprecate as necessary. GraphQL apis don't necessarily need versioning as the requests as it's much easier to continuously update them.
Re: Prisma – Database tools for modern application development
#19Back when prisma was emerging out of graphcool, every google documentation search sent me to graphcool, every graphcool page was full of broken links, and the shiny new prisma docs were unusable (including unviewable on my iPad that I use for researching tech I might use while sitting on the couch). It painted such a clear picture of a company that absolutely does not get the importance of API documentation to the success of an API that I've never been able to get myself to go back and give them a second evaluation.
Does their documentation today feel like the doc team and technical writing team have an actual seat at the table or does it still feel like the place is run by a bunch of architecture astronauts who think docs just happen after the fact?
Re: Prisma – Database tools for modern application development
#20Unless you have specific requirements, Ive always found prisms to be bloated / heavy. I prefer Hasura.
Do you have examples of specific requirements for which Prisma would be a good fit?
Prisma is good for writing data models, running migrations. The new admin is very usable already, although still beta. I've been very productive loading, editing and querying data.
Hasura I think is good for preexisting db, no migrations? I haven't evaluated it fully.