Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Prisma Raises $12M Series A

prisma.io

Post reply on HN
Print view View original

91–100 of 114 posts

Re: Prisma Raises $12M Series A

#91

Post by jasonhero »

jaeming wrote: post #88

I'm very excited about the work Prisma is doing. I didn't get it at first but after trying it out, it was the best ORM experience I've had in Javascript. It introspects your DB and generates a client that provides typescript definitions for your queries. When I try to select a non-existent field or relation, I get warned via ts. Right now it's mainly their client that is production ready but they are making great pro…

I do find the typed query builder interesting, I don't think it's fully "there" yet in terms of functionality. I think they need to ditch the whole 'definitive single state' database model and just lean hard into the typed query builder. I'd seriously consider it if they were to implement similar functionality as the Java JOOQ library.

Re: Prisma Raises $12M Series A

#92

Post by fizx »

danpalmer wrote: post #66
nikolasburk wrote: post #35

Earlier quoted context omitted.

Some of the ideas we've built into Prisma are certainly inspired by tools in other languages and we've looked a lot at LINQ and the C# ecosystem in general as we designed Prisma! However, I believe that one thing that sets Prisma apart is the architecture with a _query engine_ [1] (implemented in Rust) that takes care of query planning and execution on top of which we can add lightweight, language-specific layers to…

What exactly does your "query engine"/planner actually do? I understand the role that, for example, the Postgres query planner does. Is the idea that Prisma might be backing on to multiple databases and therefore needs another planning layer? If so, wouldn't this need to be very specific to the database and schema – knowing that particular fields in one database refer to entities in another? Does Prisma tackle this?…

I'm assuming that it's basically a port of GraphQL+DataLoader, so basically using recursive descent to manage hash joins.

Re: Prisma Raises $12M Series A

#93

Post by [deleted] »

joshring wrote: post #89
jasonhero wrote: post #85

I've been using prisma for a couple months now at my employer. The longer I use it, the more frustrated I find myself with the tool. Here's a list of a few things out of many that you can't do with this tool (Prisma Migrate): * Renaming columns/tables * Migrating data from one column/table to another column/table. * Write anything that isn't a table definition, such as procedures, functions, events, transactions, etc…

I agree, all of the "do it all" database tools have always hurt in the long term in every system I've worked on that uses them (TypeOrm, Prisma, etc..) From what I can tell it is always better to just learn and understand the database you are using and create it by hand. You may spend a tiny bit longer with basic crud boiler plate, but it will benefit you greatly in the long term to just have solid native migrations…

[deleted]

Re: Prisma Raises $12M Series A

#94

Post by rgbrgb »

markhalonen wrote: post #28

a similar open source project is Postgraphile: https://www.graphile.org/postgraphile/ I've used it on 3 non-trivial projects with great success

Played around with postgraphile a bit and love how easy it is to stand up a graphql endpoint with a ton of features. Liked it a lot more than hasura because you could use it as a library to expose a graphql endpoint on a next.js api endpoint rather than running as a separate service.

I do wonder how a project built with a lot of logic in the DB ends up evolving over time. With a Rails project (my recent professional experience) if we're tweaking a feature, I can refer a new engineer to my_feature.rb where they'll find all the logic around that feature. With triggers and functions in the DB, it seems like there's not a common notion of organizing the source code. Anyone dealt with that in the past?

The thing that's attractive to me about Prisma is that the mental model seems a lot closer to ActiveRecord and I just understand that way of working and scaling a productive team using it.

Re: Prisma Raises $12M Series A

#95

Post by broberts01 »

jasonhero wrote: post #85

I've been using prisma for a couple months now at my employer. The longer I use it, the more frustrated I find myself with the tool. Here's a list of a few things out of many that you can't do with this tool (Prisma Migrate): * Renaming columns/tables * Migrating data from one column/table to another column/table. * Write anything that isn't a table definition, such as procedures, functions, events, transactions, etc…

I have been using it for about 8months now and found that the migration portion of it isn't quite ready but is being heavily worked on.

For me, the type safety and ease of use with the api has been fantastic though. For now, I have been happy to use the client but not the migration tool. It has been built so that you don't need to do full buy in if you don't want to.

Re: Prisma Raises $12M Series A

#96

Post by anandchowdhary »

zookatron wrote: post #20

I find it odd that they say "Prisma is ready for production", but "Prisma Migrate is currently in an experimental state and should not be used in production environments". Having a robust migration management system is one of the primary things I look for in an ORM/database management tool in general. The only constant is change when it comes to business requirements, and having the ability to easily and safely chang…

There are also several important features, like literally setting a default value for JSON fields or updating the String to be longer than VARCHAR(99) or using LONGTEXT in MySQL that are still open issues.

I think the VC announcement forced them to prematurely launch 2.0.0.

Re: Prisma Raises $12M Series A

#97

Post by dllthomas »

infinite8s wrote: post #72
dllthomas wrote: post #50

Earlier quoted context omitted.

On the other hand, working at a large company I saw a many-line SQL query that had been run monthly for a long while, looked at and edited by quite a few people, which down in the middle of it was comparing (for equality) a city id and a probability. There is absolutely room for improved tooling. I have no idea whether Prisma is it.

Well better tools wouldn't have helped that, since most of the them just expose the underlying low-level DB types. Until databases support a proper type-system that doesn't just describe memory layout that kind of bug will always be an issue.

"A proper type-system that doesn't just describe memory layout" is one kind of better tool, whether built into the database or separate.

Re: Prisma Raises $12M Series A

#98

Post by databrecht »

danpalmer wrote: post #66
nikolasburk wrote: post #35

Earlier quoted context omitted.

Some of the ideas we've built into Prisma are certainly inspired by tools in other languages and we've looked a lot at LINQ and the C# ecosystem in general as we designed Prisma! However, I believe that one thing that sets Prisma apart is the architecture with a _query engine_ [1] (implemented in Rust) that takes care of query planning and execution on top of which we can add lightweight, language-specific layers to…

What exactly does your "query engine"/planner actually do? I understand the role that, for example, the Postgres query planner does. Is the idea that Prisma might be backing on to multiple databases and therefore needs another planning layer? If so, wouldn't this need to be very specific to the database and schema – knowing that particular fields in one database refer to entities in another? Does Prisma tackle this?…

Assuming something in the same vein as fizx with the addition that it's probably very similar to what Join Monster tries to solve: https://github.com/join-monster/join-monster

Re: Prisma Raises $12M Series A

#99

Post by hn_reddit_human »

jasonhero wrote: post #85

I've been using prisma for a couple months now at my employer. The longer I use it, the more frustrated I find myself with the tool. Here's a list of a few things out of many that you can't do with this tool (Prisma Migrate): * Renaming columns/tables * Migrating data from one column/table to another column/table. * Write anything that isn't a table definition, such as procedures, functions, events, transactions, etc…

I think that declarative migrations don't make sense in the real world.

You're modifying existing state so it has to be incremental.

I'm curious to see how Prisma plans to handle these real-world use-cases.

Re: Prisma Raises $12M Series A

#100

Post by gsvclass »

purplerabbit wrote: post #90
gsvclass wrote: post #12

Looking for something similar but not VC backed checkout Super Graph. It's very similar and in GO. Also it's not VC funded or even a startup just a good old open source project with a fast growing community. Super Graph can learn your DB schema and relationships and automatically compile GraphQL to a single efficient SQL query. Use it as a standalone service or a library in your own code. It also works with Rails aut…

Are there any tools out there that provide generated GQL APIs with auth provided via middleware? This looks nice, but I'm hesitant to use anything this config-file driven

That almost describes Super Graph. It's not exactly config file driven it can be used as a library within your own GO code and it's configured via a config object. In fact if you look at the example here we're passing null (nil) for the config since unless you want to do something more complex out of the box it just works config is not needed. https://supergraph.dev/docs/home#using-it-in-your-own-code
Post reply on HN