Using Prisma Client API with NextJS and a Private AWS Database backend
Our existing project uses an
AWS Private IP RDS (MySql DB) on the backend and our frontend currently uses Next.js 14.
We're fetching and patching data on the client side using API's
As a frontend dev i'd like to be able to use server actions and take advantage of the Prisma Client API for using methods like
user.findMany
We use liquibase to manage DB schema, which means we wouldn't want Prisma to start updating the schema. Validating schema would be very useful though.
Another concern is that our db connection (either with accelerate or otherwise) remains private with a Authorization / token to avoid public visibility etc.
Any insight would be greatly appreciated, note my AWS knowledge is fairly basic.2 Replies
There are two options that I’m aware of:
* use
prisma introspect to build the prisma/schema.prisma
* generate the Prisma schema via script or by hand
It doesn’t look like there are existing tools to generate a Prisma schema from liquibase, so you’d be on your own there.
Introspection is likely the way I’d go.Thanks for the response @Ustice - i'll take a look and run it by our backend dev and see what we can muster!