Prisma

Screenshot_20211111_151252.png

Hello guys, I have a doubt about the size of the Prisma Client inside a docker container in a microservice architecture, some of the microservices depends on Prisma, so the final image after building the docker image is getting more than 200mb only from the Prisma Client (node_modules/.prisma with 93mb and node_modules/@prisma with 115mb), do you guys know a better way to deal with this dependency of the Prisma Client in a microservice architecture?

I'm thinking in a solution that might work:
I will make a single microservice that expose the Prisma Client to all the other microservices that need to communicate with the Prisma Client, but to do this I will need to make a volume exposing the '@prisma/client', is it a viable solution?

Anybody else also struggling with the size when packaging docker images ... I have tried a lot, but the resulting docker images are big ...

I though see even bigger numbers (production only and only `@prisma/client`):

```255M    ./node_modules/@prisma```