Live data from Hacker News

Prisma – Database tools for modern application development

prisma.io

1–10 of 88 posts

Re: Prisma – Database tools for modern application development

#3
It'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 schema changes? Does this help if I'm building a backwards-compatible api, like Stripe's API [1]? Apologies if this is already answered in your docs.

[1]: https://stripe.com/blog/api-versioning

Re: Prisma – Database tools for modern application development

#4
I've been using Prisma in for some months now (even in production), and I'm a big fan of the product. With TypeScript you have an easy full autocompletion & type checking over your models, and coupled with a graphql-yoga server & graphqlgen for the exposed GraphQL part it has been a pretty nice experience.

The downside is (because there is always some), as it's a new tech, problems can pop up and more research have to be made compared to a more old and popular framework.

In any case, I highly recommend you to try it on your own, I'm looking foward to its futur improvements.

Re: Prisma – Database tools for modern application development

#6
post #3

It'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…

Because the schema is updated on the Prisma server, I do think it could be possible to have multiple Prisma server running with different schema version.

The only issue that we did encounter so far is that it doesn't know play well easily when you have more than one instance of a Prisma server behind a load balancer that your backend connect to.

Post reply on HN