nikolasburk

17 ms·

91.
by nikolasburk 7y ago
Check out `graphql-binding`: https://github.com/dotansimha/graphql-binding
92.
by nikolasburk 7y ago
While TypeScript isn't perfect, it surely is a major step forward compared to plain JS! Newer features like conditional types and mapped types open up new possibilities. My colleague actually recently gave a fantastic talk about these
93.
by nikolasburk 7y ago
Prisma 1 indeed has a couple of quirks that we're currently ironing out with Prisma 2 (or the "Prisma Framework" as we now call it). Would love to hear from your whether the new version actually solves your pain points! Feel
94.
by nikolasburk 7y ago
Thanks for the hint, we'll update the article! :)
95.
by nikolasburk 7y ago
GraphQL is a really important use case for Prisma. That is using Prisma as the "data layer" on top of your database when implementing a GraphQL server (e.g. using Apollo Server). However, it's not the only use case since
96.
by nikolasburk 7y ago
Nikolas from the Prisma team here! Thanks a lot for the endorsement, we're indeed super excited about the current database space and the tooling we see emerging. For anyone that wants to check out what we're up to, you can find ev
97.
by nikolasburk 7y ago
I really like your point about type-safety! I think one major issue with the current ORMs in the Node.js/TypeScript ecosystem (Sequelize, TypeORM, ...) is that they're not fully type-safe. As you mention, TypeORM is definitely a s
98.
by nikolasburk 7y ago
knex.js is another example of such a query builder library in the Node.js ecosystem
99.
by nikolasburk 7y ago
Fully agree! Some mapping code is _required_ in your application, otherwise it wouldn't be able to talk to your database at all. However, I've never understood why people write this mapping code manually. I believe in code generat
100.
by nikolasburk 7y ago
This is a great article, I've really enjoyed reading it! I want to react to a few of the points made in the post, and point out some potential techniques for solving them! Most ORMs are heavily inspired by object-oriented programming w
101.
by nikolasburk 7y ago
What this article misses IMO is a clear distinction of the various abstractions layers an ORM can provide, most importantly these two: - Heavy ORMs : Object-oriented mapping layers that map classes to tables. A record is represented as a
102.
by nikolasburk 7y ago
What a great article, this paragraph really reasonated with me: > Any situation where complex functionality is wrapped in another layer runs the risk of increasing the overall complexity when the wrapping layer is itself complicated. Thi
103.
by nikolasburk 8y ago
(I work at Prisma) Prisma is open-source and you are typically running it in production by running it on your own cloud infrastructure. The commercial parts of Prisma are called Prisma Cloud and Prisma Enterprise. Prisma Cloud aims to simpl
104.
by nikolasburk 8y ago
Thanks a lot for this feedback and great to hear you like the code-first approach of GraphQL Nexus for building your GraphQL server! For anyone who is curious about Nexus, I recommend our blog article series about code-first vs SDL/sch
105.
by nikolasburk 8y ago
Thanks so much for your positive feedback, we really appreciate it! We indeed have many exciting improvements in the store, to get an overview of those feel free to check out our RFCs: https://github.com/prisma/rfcs Al
106.
by nikolasburk 8y ago
(I work at Prisma) That's a great question! We started with a major focus on GraphQL which has now become more generic as Prisma can really be used for any app that uses a DB (REST, gRPC, ...). With that GraphQL history, we've put
107.
by nikolasburk 8y ago
I work at Prisma, we've recently written a blog post about exactly this question where we also compare Prisma to other services like Hasura or AWS AppSync: https://www.prisma.io/blog/prisma-and-graphql-mfl5y2r7t49c
108.
by nikolasburk 8y ago
I work at Prisma and it's really awesome to hear such feedback! Please let us know if you have any further questions, we're happy to help :)
109.
by nikolasburk 8y ago
(I work at Prisma) It is very important to understand that Prisma is NOT a GraphQL-as-a-Service like Hasura or Postgraphile. It's really a suite of database tools that you can use for any use case (building GraphQL, REST or gRPC APIs,
110.
by nikolasburk 8y ago
This is a very common question, we actually recently wrote a blog post about exactly this topic: https://www.prisma.io/blog/prisma-and-graphql-mfl5y2r7t49c/ Hopefully that clears it up!
111.
by nikolasburk 8y ago
Thanks a lot for the feedback Max, we really appreciate it! We're currently working on many improvements (e.g. a more powerful data modelling syntax, a sophisticated migration system, opening up the database connector and client genera
112.
by nikolasburk 8y ago
(I work at Prisma) Thanks a lot for the positive feedback, we appreciate it a lot! As to your question, I assume with "backend schema" you're talking about the Prisma datamodel? Whenever you change the datamodel, you're
113.
by nikolasburk 8y ago
I totally agree with this and this is actually very relevant for us at Prisma as we're supporting various kinds of databases. Our goal isn't to have one universal data access abstraction, but instead we want to ensure developers s
114.
by nikolasburk 8y ago
I work at Prisma and this is one of the questions we're currently hearing the most (we'll actually publish a blog post about this exact question soon). Generally, think of Prisma as a suite of database tools that simplify workflow
115.
by nikolasburk 8y ago
(I work at Prisma) It's true that we haven't focussed on a mobile experience for the docs so far (assuming a primary use case for the docs is when being used on your computer as you're using Prisma). However, we see that many
116.
by nikolasburk 8y ago
We wrote about this a while a ago on the Prisma blog: https://www.prisma.io/blog/top-5-reasons-to-use-graphql-b60c...
117.
by nikolasburk 8y ago
Be aware that MDG is now almost entirely shifting their attention to GraphQL and Apollo. I don't think Meteor.js will be maintained much longer.
118.
by nikolasburk 8y ago
Backend: GraphQL + TypeScript with Prisma on top of a MongoDB/PostgreSQL Frontend: React / React Native + Apollo Client Then use 3rd-party services for the "standard" parts of your business logic (like Auth0 for authenti
119.
by nikolasburk 8y ago
Yes :) https://github.com/prisma/prisma
120.
by nikolasburk 8y ago
Go is a great language for building GraphQL servers, the https://github.com/99designs/gqlgen library helps you by build type-safe GraphQL servers and reduces the boilerplate. You can find an example here: https:/

More ›