Reuse a CDK project and make it scalable with the best practices

[oscar1518]

Hi guys!

I'm quite new to the CDK, I started building my API for a small app for managing appointments for a friend's small business, it's a very simple project, but it made me see the power of AWS. The issue is that I use Cognito, ApiGateway, Lambda and DynamoDB, up to this point everything was going great until I considered reusing this same project in another business of the same style. I have seen that by iterating through the stack, I can generate the same tables and adapt them to have them duplicated in both businesses, since I am interested in using separate UserPools, such as apis, etc. It doesn't seem like a good practice to me, but I have seen that if I make changes to the structure, I can upload all the changes at once, adapting them to each company, but with about 30-40 endpoints, it has already started to take me about 10 minutes per company to deploy changes.

Do you have a better idea of being able to use my CDK in a more efficient and scalable way?

Thank you guys!

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.