sorenbs

PlanetScale is the serverless relational database we have been waiting for all this time. It's truly excellent, and being based on the same tech that runs youtube, we know it will scale well.

Many prisma.io users tell us that they use prisma to implement complex business logic and then stitch it all together in hasura which exposes the final graphql API.

So it might even be feasible to use Hasura for more complex applications. I'm curious if there are specific reasons you see this not working well?

Imagine looks super cool!

Prisma has Mongo support coming really soon, and we will be speaking more about it at https://www.mongodb.com/live in July.

Other NoSQL and relational databases to follow, but we have no timeline for that yet.

I have been using the beta version of PlanetScale for a while, and it is extremely cool. It's using the mature technology that powers Youtube to provide a developer experience for databases similar to what Vercel and Netlify provide for hosting: It will give you a database branch for each Git branch and help you manage the workflows around it.

And it is the first truly serverless relational database offering that I am aware of. The cost scale to 0, so it is perfect for small projects, but that same instance will scale to support massive load when you need it.

Prisma does not use a class hierarchy that are mapped directly to tables. Instead we take advantage of structural typing to give you a very smooth developer experience that is faithful to the relational model.

There are pretty extensive docs on how Prisma optimises n+1 queries: https://www.prisma.io/docs/guides/performance-and-optimizati...

There are many discussions on reddit about Prisma vs TypeORM in particular. For example here: https://www.reddit.com/r/node/comments/l3xu6w/is_prisma_a_vi...

There is also a good discussion going on here: https://www.reddit.com/r/node/comments/l00fit/what_do_you_th...

A quote:

> Once you start working with the Varnish source code, you will notice that Varnish is not your average run of the mill application.

> That is not a coincidence.

> I have spent many years working on the FreeBSD kernel, and only rarely did I venture into userland programming, but when I had occation to do so, I invariably found that people programmed like it was still 1975.

> So when I was approached about the Varnish project I wasn’t really interested until I realized that this would be a good opportunity to try to put some of all my knowledge of how hardware and kernels work to good use, and now that we have reached alpha stage, I can say I have really enjoyed it.

Thank you!

SchemaHero looks super interesting. I'll check with the team to make sure they take a look. Introducing a Kubernetes operator is pretty ambitious.

The Prisma Migrate team is thinking about these issues. I'll let them elaborate when they wake up tomorrow :-)

We are taking inspiration from this great writeup on how Github has implemented a workflow that enable their developers to collaborate on Schema Migrations at scale: https://github.blog/2020-02-14-automating-mysql-schema-migra...

Hi there,

I think Prisma might cover "smart many2many relationships". What exactly do you mean by smart caching techniques? Prisma is applying the dataloader pattern from GraphQL automatically under the hood, which we find to be a much easier thing to reason about compared to all the complexity of multi-tiered caching in Hibernate.

The dependent field requirement is super interesting, and something we will tackle in the future based on Change Data Capture. With Prisma you will be able to write a simple declarative data transformation, and the system will automatically keep the field up-to-date, even if the database is changed by another application, or manually by a user.

Hope that makes sense? :-)

Thanks for the details!

We would price such a service to be competitive with the obvious alternative of using a long-running VPS or ec2 instance.

Really interesting.

How do you deal with ephemeral file storage? I guess you actually need the provider (say AWS) to build this into the platform?

Hi Picardo!

We are toying around with the idea of launching a Cloud SQLite product targeting this exact use case.

How large are your data sets?

Would you be interested in a quick call to discuss your needs in more detail?

Thank you!

Is it a concern that both Tokio and stdlib have AsyncRead+AsyncWrite traits that seem to be incompatible?

I'm not sure why Prisma is called out here. But posts like this bubble up in our Slack, so I thought I should respond...

Prismas query engine is a complex piece of code and receives very little outside contributions. Moreover, Prisma only has bindings for JS/TypeScript and Go at the moment, so there is no way to consume Prisma from Scala. As a result, very few Scala developers know about Prisma.

We enjoyed Scala as a language, and the massive JVM ecosystem is a huge benefit. That said, we were forced to rewrite the query engine in Rust as we had a need for a more modular architecture enabling us to embed parts in JS and Go libraries. We looked at the Scala Native and Graal projects (spent 6 months building a prototype), but neither delivered a sufficiently low memory footprint. The Prisma2 rewrite to rust is a much more stable product, and we love the Rust language.

All the best to both the Scala and Rust ecosystems. Hugs.

After spending a year rewriting Prisma from Scala to Rust, we finally launched it in June this year. The reception has been phenomenal, but there was one piece missing. Without a solid integrated Database Migration Tool, Prisma wasn't a complete ORM solution.

Prisma Migrate is finally ready, and it is a much better product than what we shipped in Prisma 1. I look forward to hear your feedback!

I tried both the previous gen and newest version of Vanmoof and Cowboy. I do not like the automatic gear shifting in Vanmoof one bit. The Cowboy is single-speed gear and the motor intelligently adjust the level of support so you don't feel the lack of gears. This gives a super smooth experience, and I honestly expect all electric bikes to transition to this setup over time.

What would this do? What is your use case?

It sounds like Vectorized is a streaming platform built on top of Redpanda. Is that the right way to think about it? If yes, then why not build it directly on top of Kafka instead?

Contact info is in my profile. Please send an email so we can set something up :-)

This is a really cool project. I’m happy to see that you are using Prisma for data access. If you are interested we can set up a shared slack channel so you can provide feedback and we can make sure we support everything you need for this project :-)

The narrative that diesel cars are better for the environment, which is pushed by the scientists who found the 11-15 tonnes was disputed by your article. From the first section:

“The Belgian newspaper De Standaard published this claim on their website on the 18th of April. We rate this claim as mostly false.”

Again, even if the cost of b battery production in Germany two years ago was 15 tones, it doesn’t matter. Why? Because Germany made almost no car batteries two years ago, and the grid is rapidly decarbonising - in Germany and most of the world.

Now, if you are arguing that it would be better if people lived closer to where they work, and stopped driving cars altogether - I’d agree with that. But cars will continue to be with us for a long time, and the Sonne we can transition the fleet to electric the better.

Sure, but the total system loss for hydrogen is much higher, so unless renewable electricity becomes free, batteries win on tco.

The 11-15 Tonnes come from the study that you referenced page is disputing?

There is a persistent narrative in Germany that diesel cars are better for the environment, and your comment is playing into that. This narrative is wrong and damaging.

Why are you doing this?

Sounds like you need to follow Auke on Twitter :-P

He has literally spent the last five years debunking this nonsense. Here's a thread from just 5 hours ago: https://twitter.com/AukeHoekstra/status/1279359481177083904

TL;DR: These comparisons always use too much energy for battery production, too high efficiency for gasoline cars, and fail to take into account that the grid is rapidly decarbonising, even in backwater countries like USA. Your source claims 20 tonnes for battery production, but reality is around 6 tonnes and falling due to grid decarbonising.

Kevas is asking why he would use Prisma instead of raw SQL. There are numerous user testaments on this very page from developers explaining why they prefer Prisma over raw SQL. But it is much more fun to just call us "gobbledegook" instead of engaging with the people who are right here.

If you scroll down the page, you will see a different thread where Kevas compare Prisma to left-pad.

Kevas is a grumpy HN troll, and I have no patience for that.

As you will see from all other interactions on this page, on twitter and on our 30.000 developer strong Slack community, we engage happily and constructively with anyone who comes with curiosity and an open mind. But if you come with negativity we will ask you to find another community to hang out in.

Was it though?