*deep sigh* if you put everything in a single lambda function you have negated the benefit of isolation of using lambda functions
-
Show this thread
-
getting over the server metaphor is gonna be an uphill climb; which makes sense. hard to imagine monoliths being a bad pattern… I guess.
4 replies 0 retweets 2 likesShow this thread -
get suggested about once per day to 'just put everything in one lambda' which was where we started. that path is possible. but slow/brittle.
2 replies 0 retweets 1 likeShow this thread -
-
Replying to @chrismunns @brianleroux
I would like to signup for this army.
2 replies 0 retweets 1 like -
ooh
#ServerlessSamurai assemble! With#Samurai Jeff as our token leader :)1 reply 0 retweets 4 likes -
Replying to @ajaynairthinks @mweagle and
Ooooh
#SamuraiJeff needs to be created. Someone mention this to@IamStan ... I want to be in this army too.1 reply 0 retweets 3 likes -
Replying to @PaulDJohnston @ajaynairthinks and
I constantly have to tell people not to put everything in one lambda. The problem is it might be a thing that needs to be experienced
2 replies 0 retweets 4 likes -
Replying to @PaulDJohnston @ajaynairthinks and
FWIW we went the opposite direction. Lots of lambdas -> one lambda that does lots of things
2 replies 0 retweets 0 likes -
Replying to @southpolesteve @ajaynairthinks and
Interesting. Would be interested as to why you chose that route and whether it's been of value
3 replies 0 retweets 0 likes
Another thing we do is build multiple lambdas from one code base with webpack. Deploy 3 variants of our main graphQL fn this way.
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.