Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
Mono-Lambda vs Single-Function isn't a hard-and-fast choice, but rather a spectrum, with most users trying a combination of both in the long term.
I'm glad you made this point, as I certainly see it as a broad spectrum, rather than a polar debate. When you put common utils (logging/monitoring utils, libraries, core framework stuff) into shared packages, you can then leverage that to have distinct infrastructure and much of the benefits, whilst retaining the benefits of shared-code in a monolithic approach. And mono repo helps with this. Obviously sharing business logic is a real double-edged sword, and one to be avoided!
Nice write-up AJ!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm glad you made this point, as I certainly see it as a broad spectrum, rather than a polar debate. When you put common utils (logging/monitoring utils, libraries, core framework stuff) into shared packages, you can then leverage that to have distinct infrastructure and much of the benefits, whilst retaining the benefits of shared-code in a monolithic approach. And mono repo helps with this. Obviously sharing business logic is a real double-edged sword, and one to be avoided!
Nice write-up AJ!