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

41–50 of 114 posts

Re: Prisma Raises $12M Series A

#41

Post by desmap »

Related and FWIW: I checked all solutions in this space and I stuck with type-graphql which is not only an amazing lib but offers a clean architecture:

Decorated Typescript types as classes dictate the GraphQL schema and the DB model (either through further decorator libs or custom solutions). So, you end up with only one source of truth + stay DRY + very low level of abstractions. There is some debate around the right approach but I much prefer this approach over the others such as DB-model-first (Hasura) or Prisma 2 which I remember has its own DSL for modeling data.

Re: Prisma Raises $12M Series A

#42

Post by jrumbut »

bovermyer wrote: post #14

The graphic under "Database tools are stuck with legacy paradigms" made me chuckle. Just because the tech under the "Legacy" column isn't the new hotness doesn't mean they're suddenly irrelevant or even a bad choice.

Yeah when I got there I went from curious to put off. That was the place to put an example showing something impressive rather than an iffy summary of web dev trends.

I clicked around a bit. I heard a lot about motivations but couldn't figure out a specific situation where I would be really happy to be using Prisma.

Re: Prisma Raises $12M Series A

#43

Post by lordofgibbons »

kevas wrote: post #13

I’m not seeing why I’d use this over sql. Can someone please enlighten me as I find this to be much more gobbledegook than sql.

My first instinct was to say type safety, but you don't really get that with JS either way.

Maybe it would be popular for new engineers that don't feel like learning SQL. Same reason why MongoDB got popular.

Re: Prisma Raises $12M Series A

#45

Post by RedShift1 »

abraxas wrote: post #32
jordanab wrote: post #25

While the implementation certainly seems very nice, the ideas behind Prism 2 aren't particularly new, or unique for that matter. For example the .NET ecosystem already has (for a long time) most of the stuff that is presented as being uniquely offered by Prism: generated database clients (LINQ-to-SQL, Entity Framework), generated data models (EF POCO's), type-safe queries (LINQ) etc.

Everything is being reinvented from scratch in the JS world. The insistence on unifying into one language means that a lot of tried tested and true has been tossed aside and it's all being rebuilt sometimes with dubious benefit.

And at the end of the day all we do is select, insert, update and delete in some database.

Re: Prisma Raises $12M Series A

#46

Post by hypewatch »

kevas wrote: post #13

I’m not seeing why I’d use this over sql. Can someone please enlighten me as I find this to be much more gobbledegook than sql.

These types of tools are effectively another way to parameterize your SQL that _feels_ more like writing in your scripting language (nodejs in this case)

This approach is notorious for generating inefficient sql queries, but it can improve jr fronted dev productivity b/c a tool like this is easier to learn than SQL.

Re: Prisma Raises $12M Series A

#47

Post by nikolasburk »

desmap wrote: post #41

Related and FWIW: I checked all solutions in this space and I stuck with type-graphql which is not only an amazing lib but offers a clean architecture: Decorated Typescript types as classes dictate the GraphQL schema and the DB model (either through further decorator libs or custom solutions). So, you end up with only one source of truth + stay DRY + very low level of abstractions. There is some debate around the rig…

TypeGraphQL and Prisma are not really comparable though. Prisma is an open-source database toolkit (much like an ORM), TypeGraphQL is a GraphQL schema construction library (like `graphql-js` or `@nexus/schema`), they solve very different problems!

You can even combine Prisma with TypeGraphQL if you're building a GraphQL server that needs to access a databases. In that case, you'd use Prisma Client inside your TypeGraphQL resolvers to send database queries.

In fact, we are collaborating with the maintainer of TypeGraphQL to build an integration between Prisma and TypeGraphQL that will allow you to leverage information from your Prisma models when building your GraphQL schema! :)

Re: Prisma Raises $12M Series A

#48

Post by hypewatch »

sorenbs wrote: post #2

Prisma co-founder here. I’m really excited to put this to good use and roll out many new futures in the coming months. Happy to answer any questions :-)

Why fundraise against the Prisma open source project instead of creating a new brand for the premium / enterprise product? Like how Confluent is separate from Kafka.

As a developer, I prefer the Confluent/Kafka model because it’s crystal clear where the separation is between premium and open source.

Re: Prisma Raises $12M Series A

#49

Post by Sujan »

bovermyer wrote: post #14

The graphic under "Database tools are stuck with legacy paradigms" made me chuckle. Just because the tech under the "Legacy" column isn't the new hotness doesn't mean they're suddenly irrelevant or even a bad choice.

I don't think the table indicates "irrelevant or even a bad choice" at all - it just puts "old" and "new" next to each other.

No reason not to use the older things if they work for you. But if they don't, never choices might help.

Re: Prisma Raises $12M Series A

#50

Post by dllthomas »

pphysch wrote: post #33
nikolasburk wrote: post #15

Earlier quoted context omitted.

I feel like current database tools don't really cut it! From my own experience, working with databases in Node.js and TypeScript has always been a painful experience – sometimes more, sometimes less, but it was never smooth or enjoyable! With Prisma, we're setting out to build database tools that make developers more _confident_ and _productive_ [1] in their database workflows! We're focusing on type-safety, intuitiv…

> working with databases in Node.js and TypeScript has always been a painful experience Even after reading your (three) paragraphs from the article on why raw SQL and drivers are bad, I'm far from sold. 1. Establish connection 2. Execute SQL 3. Manipulate results 4. More SQL/Commit/close IME a lot of the struggle comes from not understanding how 1. or 2. work and trying to do all the heavy lifting in 3. The amount of…

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.

Post reply on HN