*deep sigh* if you put everything in a single lambda function you have negated the benefit of isolation of using lambda functions
FWIW we went the opposite direction. Lots of lambdas -> one lambda that does lots of things
-
-
Interesting. Would be interested as to why you chose that route and whether it's been of value
-
I think graphQL is part of it too. One endpoint and one big lambda is a very happy path.
-
I can totally see that for API reads. Not convinced for writes, text/html verbs, events, triggers, or scheduled fns.
End of conversation
New conversation -
-
-
... but we do still have separate lambdas for some slow/complex bits. Do what makes sense for you! Feel your own pain. Respond. Repeat.
-
FWIW I'm a fan of Lambda monolith as an on ramp
Works well with existing, well-known frameworks (Express, Flask) but cheaper than Heroku -
And a good way to learn + explore Lambda!
-
yea, but like putting an entire program in a single file probably not the right long term habit to build
-
Yep, agree with that
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
