My lambda layer for running my app and migrations ...
# prisma-migratem
Mischa
08/10/2021, 9:28 AMMy lambda layer for running my app and migrations - bummer that the dependencies for prisma clock in at 80MB š©
(not counting @prisma/sdk or @prisma/migrate)
r
Ryan
08/10/2021, 10:05 AM80 MB Zipped?
m
Mischa
08/10/2021, 10:05 AMUncompressed
r
Ryan
08/10/2021, 10:10 AMDeleting
@prisma/enginesm
Mischa
08/10/2021, 10:11 AMYes but if I remove the engine binaries then my migrations and app donāt work
Mischa
08/10/2021, 10:12 AMThis is a layer for my application
p
Pierre Ortega
08/10/2021, 8:16 PMis it a requirement to have your migrations working on this layer?
m
Mischa
08/11/2021, 8:06 AMNot really no
Mischa
08/11/2021, 8:07 AMI was trying to use the NodeJsLambda construct to bundle @prisma/migrate and @prisma/sdk with my migration function, however they try to import ā../package.jsonā which is a pain but I found a workaround. but I still need the binary and my release takes the same time either way since itās just moving from one part of the deployment to another
Mischa
08/11/2021, 8:08 AMit just seems weird to need 90MB of binaries to do this stuff i guess
p
Pierre Ortega
08/11/2021, 6:34 PMI would suggest separating them. Try to keep your runtime layer as minimum as possible by running migrations somewhere else and removing from this layer. is this possible?
plus one +1 1
r
Ryan
08/12/2021, 6:18 AMI agree! Having separate lambdas for querying and migrations would make this much better. Also imo in this case, layers arenāt required. Bundling it with the Lambda would be better.
9 Views