So yeah, after that conversation I genuinely think that "Framework as a Service" describes what's interesting about the shift.
-
Show this thread
-
Instead of running the framework in your process (which gives dev flexibility in exchange for ops cost) move the fwk into the platform.
1 reply 0 retweets 3 likesShow this thread -
That probably slows down the vibrancy of framework evolution, but 13+ years after Rails it makes sense to bake it in for many people.
1 reply 0 retweets 2 likesShow this thread -
I just hope that that doesn't mean we become reliant on Amazon (closed source) to add important fwk features we used to be able to do OSS.
6 replies 0 retweets 4 likesShow this thread -
Replying to @wycats
Lambda support exists at language level, not framework level. You're not really locked into framework features unless that changed?
1 reply 0 retweets 0 likes -
Replying to @lsegal
You are because you can't (or shouldn't) run stuff like a router inside your function. So you're reliant on Lambda to perform the role ...
2 replies 0 retweets 1 like
traditionally filled by in-process frameworks.
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.