backend devs: serverless is coming for you toohttps://twitter.com/JoeEmison/status/985583754419818496 …
-
-
Replying to @southpolesteve
One of my favorite parts in choosing these architectures is that it's way easier to avoid the brogrammers when you aren't hiring anyone for the back end. I find almost no brogrammers amongst the front-end devs.
1 reply 0 retweets 5 likes -
Replying to @JoeEmison
For sure! The industry likes to crap on frontend work which pushes brogrammers to the backend. Front end developers will have the last laugh when the brogrammers are begging for help learning CSS
2 replies 1 retweet 11 likes -
Replying to @southpolesteve @JoeEmison
I spent the last 2 years doing serverless architecture and tooling work. my new job is doing front end UI work. The list of reasons for that shift is long and complex. But this conversation speaks to some of it.
1 reply 0 retweets 8 likes -
Replying to @southpolesteve @JoeEmison
Don’t you think in some respects serverless results in more backend code? SOA by default is non-trivial for small apps and MVPs
1 reply 0 retweets 0 likes -
Replying to @danbucholtz @southpolesteve
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.
1 reply 0 retweets 2 likes -
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.
2 replies 0 retweets 1 like -
Replying to @JoeEmison @danbucholtz
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.1 reply 0 retweets 0 likes -
Replying to @southpolesteve @JoeEmison
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?
2 replies 0 retweets 0 likes -
Replying to @danbucholtz @JoeEmison
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.
1 reply 0 retweets 0 likes
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.
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.