Also doing my deploys/destroy outside of github ac...
# sstj
Julien Goux
03/05/2021, 9:39 PMAlso doing my deploys/destroy outside of github actions would make sense
f
Frank
03/05/2021, 9:49 PM
I remember from your architecture you were deploying ESC fargate, i guess that’s what took the longest to provision.
Frank
03/05/2021, 9:51 PM
CDK deploys all stacks sequentially one after another. If ur CDK app has stacks that aren’t interdependent, SST will deploy them concurrently. And you might see a speed boost there.
Frank
03/05/2021, 9:51 PM
Subsequent deployment shouldn’t take this long.
j
Julien Goux
03/05/2021, 10:01 PMMy stacks are dependents from each others
Julien Goux
03/05/2021, 10:02 PMI think I'll need to build a "common stack" that I keep around like the vpc, aurora, cloudfront
Julien Goux
03/05/2021, 10:03 PMAnd a preview stack which handle the most dynamic part like lambdas and fargate
Julien Goux
03/05/2021, 10:04 PMYes subsequent deploys are faster of course 🙂
f
Frank
03/05/2021, 10:32 PM
Yeah that makes sense!
j
Julien Goux
03/06/2021, 10:51 PMI deployed a second time, I think the longest parts are the VPC creation with the NAT gateways and Aurora serverless
Julien Goux
03/06/2021, 10:51 PMalso I’m currently not using codepipeline so cdk deploy is doing 0 parallel deployment 😞
Julien Goux
03/06/2021, 10:51 PMit took 27 min again, at least the timing is the same every time lol
f
Frank
03/06/2021, 10:52 PM
LOL very positive thinking 😁
j
Julien Goux
03/06/2021, 10:52 PMmy architecture evolved quite a bit since the last time I show you my diagram, I’ll need to update it and show you again ^^
Julien Goux
03/06/2021, 10:54 PMBasically Cloudfront as a reverse proxy to both my frontend and backend. The backend is a fargate service fronted by an ALB. And I have a a private ApiGateway + lambdas that communicate with the fargate service
Julien Goux
03/06/2021, 10:54 PMI had to implement fun patterns to make all of these works
Julien Goux
03/06/2021, 10:54 PMLike making a private ApIGateway, or protecting the ALB to be accessed outside of Cloudfront 😄
Julien Goux
03/06/2021, 10:55 PMAlso I didn’t see a lot of documentations / examples about using Cloudfront as a reverse proxy for the backend too but I think it makes sense and open a lot of interesting caching opportunities 🙂
Julien Goux
03/06/2021, 10:56 PM(also no CORS :p)
f
Frank
03/06/2021, 10:57 PM
yeah… this is awesome! I was asked by a few folks about setting up Hasura on lambda.. i’d love to have a peak at ur CDK code at some point, and maybe make it a Hasura Construct out of it.
j
Julien Goux
03/06/2021, 10:58 PMSure, I’ll have to make sure everything is working smoothly but happy to share 🙂
Julien Goux
03/06/2021, 10:58 PMHasura is hosted in fargate but I have an internal graphql API stitched to Hasura as a remote schema for my business logic
Julien Goux
03/06/2021, 10:58 PMthis one is in a lambda
Julien Goux
03/06/2021, 10:59 PMHasura in a containerized lambda could work on paper but as it provides subscriptions features (websocket) I don’t think it would fit at all
f
Frank
03/06/2021, 11:03 PM
Yup. it’s impressive you just dived in and managed to put something together so quickly. There are quite a few moving pieced there.
j
Julien Goux
03/06/2021, 11:05 PMWell, with CDK it’s quite magic, it’s just code 😎
f
Frank
03/06/2021, 11:06 PM
right.. and you don’t have to define every single CloudFormation resource
j
Julien Goux
03/06/2021, 11:06 PMFor my job consuming lambdas I can just loop over my “workers” folder and create them dynamically (SQS + Lambda for each worker), it’s so cool.