4 ms·

Frontend - React / TypeScript Backend - Lambda / TypeScript Infrastructure - AWS CDK / TypeScript Kept in a monorepo, which means tightly-coupled code-sharin

Frontend - React / TypeScript Backend - Lambda / TypeScript Infrastructure - AWS CDK / TypeScript Kept in a monorepo, which means tightly-coupled code-sharing between all the different components. Definitely has it's negatives - but being in small startup (solo technical) also means lots of interruptions and chopping and changing. Having one language, stack, and repo makes it much easier to me to start, stop, and pick things up as I go.

madamelic 7y ago
>monorepo, which means tightly-coupled code-sharing between all the different components. It's funny how one persons dream is another person's nightmare. Tightly coupled software is horrifying to me. Modularization all the way; define contracts then build away.
- jwilliams 7y ago
  Tightly-coupled doesn't necessarily mean you don't have contracts. In this case, the contract is shared TypeScript types between the front and back-ends. This means you can statically verify as much as the type system allows.
alepacheco 7y ago
I use a similar stack of React/TS and Node/TS using the Next.js library. It makes it really easy to get started because you don't need any configurations files. I made a template if you like the idea https://github.com/alepacheco/landing-template https://github.com/alepacheco/landing-template
moltar 7y ago
How’s your experience with CDK? I’ve been looking at it a few times and it felt a bit raw and not well documented yet. Did you have a solid AWS experience prior?
- jwilliams 7y ago
  CDK experience has been mixed. Prior to GA it was all over the place, but it's gotten more stable now. A lot of cloudformation quirks leak directly into CDK. And I've learned to be patient (e.g. one change at a time, roll though all environments, do adds and deletes separately...). Right now using it is 50/50 for me. I'm assuming as more construct libraries become commonplace that will help the most (up until recently this was hamstrung by the amount of breaking changes)
  - moltar 7y ago
    Thank you for the feedback!

madamelic 7y ago

>monorepo, which means tightly-coupled code-sharing between all the different components. It's funny how one persons dream is another person's nightmare. Tightly coupled software is horrifying to me. Modularization all the way; define contracts then build away.

jwilliams 7y ago
Tightly-coupled doesn't necessarily mean you don't have contracts. In this case, the contract is shared TypeScript types between the front and back-ends. This means you can statically verify as much as the type system allows.

alepacheco 7y ago

I use a similar stack of React/TS and Node/TS using the Next.js library. It makes it really easy to get started because you don't need any configurations files. I made a template if you like the idea https://github.com/alepacheco/landing-template https://github.com/alepacheco/landing-template

moltar 7y ago

How’s your experience with CDK? I’ve been looking at it a few times and it felt a bit raw and not well documented yet. Did you have a solid AWS experience prior?

jwilliams 7y ago
CDK experience has been mixed. Prior to GA it was all over the place, but it's gotten more stable now. A lot of cloudformation quirks leak directly into CDK. And I've learned to be patient (e.g. one change at a time, roll though all environments, do adds and deletes separately...). Right now using it is 50/50 for me. I'm assuming as more construct libraries become commonplace that will help the most (up until recently this was hamstrung by the amount of breaking changes)
- moltar 7y ago
  Thank you for the feedback!