backend devs: serverless is coming for you toohttps://twitter.com/JoeEmison/status/985583754419818496 …
-
-
Don’t you think in some respects serverless results in more backend code? SOA by default is non-trivial for small apps and MVPs
-
I disagree. Look at sample Firebase or AppSync apps that use thick clients (React, React native, iOS, Android). Most have zero back end code; all configuration.
-
But I do think that your perspective—maybe born from doing a lot of RoR or other thick-middle-tier dev?—is the one that leads to the bespoke-function-heavy serverless architectures.
-
This is where I came from and it took me a long time to get away from the mindset.
@danbucholtz to your point I think serverless is a bit orthogonal. Certainly possible to build a serverless backend heavy SOA. The tooling/best practices that will prevent that are still emerging. -
I meant the exact opposite. Wouldn’t you no matter what have a SOA since each function is an independent deployment or a micro-service?
-
Hmm. I think lots of services does not necessarily translate to more lines of backend code. Certainly possible to compose many small simple funcs that glue together services. Tooling helps those feel less distinct in dev.
-
Like Bustle's architecture is started as a monolith that gets split into serverless funcs via webpack. Or you can make one massive func (which is how things were headed with graphQL func). Serverless doesn't care much which one you do. Tradeoffs with both.
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.