Then the “infra” package would just consume those ...
# generalj
Julien Goux
12/18/2021, 12:46 PMThen the “infra” package would just consume those constructs and stitches everything in order to deploy the whole thing as a single stack.
f
Frank
12/18/2021, 1:08 PM
Ah I see what u mean. Having constructs live with the Lambda code, and have the “infra” package merge all the constructs and genearate a stack out of it?
j
Julien Goux
12/18/2021, 1:12 PMYes exactly!
Julien Goux
12/18/2021, 1:13 PMIt couples the code with its deployment target a bit, but at least the infra package doesn’t have to know about all the specifics of each service.
Julien Goux
12/18/2021, 1:14 PM(also we’re all in on AWS so I don’t mind having bits of infra in my packages lol)
f
Frank
12/18/2021, 1:15 PM
Only downside I can see is that it’d be tricky for the constructs in services to share stuff between each other
j
Julien Goux
12/18/2021, 1:25 PMI need to make a little audit about it, but I don’t think they’re sharing domain specific things
Julien Goux
12/18/2021, 1:25 PMIt’s often infrastructure interfaces coming from cdk itself