21–30 of 114 posts
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.
Earlier quoted context omitted.
The way I think about this is that the old generation of DB tools make it possible for application developers to use databases. With Prisma we want to make it a delight. There are an order of magnitude more application developers today than just 10 years ago. This enable us to invest much more in the tools we all use, resulting in higher quality and a much better experience. So to turn it around - why _not_ build new…
Because someone will build tools off yours and then someone will build tools off theirs. Abstractions on abstractions on abstractions.
Is that supposed to be a reason against? Enabling further progress sounds more like a reason for, not a reason against.
I had a look over the quick start guide and the syntax looks almost indentical to Mongoose. Why is it "next generation" compared to Mongoose?
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 :-)
Is this meant for the average developer or for highly-scalable enterprises only? What is the problem with the current vast number of databases? I personally still use MySQL and MongoDB and don't have many complaints in regards to usability or performance.
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…
I've used it on 3 non-trivial projects with great success
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.
If you liked the developer experience in the .NET ecosystem but find yourself needing to work with JavaScript or Go, you'll probably like Prisma.
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…