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.
-
-
-
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
-
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.
-
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?
- 2 more replies
New conversation -
-
-
-
Given your experience
@brianleroux, would you recommend Lambda? Would you recommend it still if I said typescript was a requirement for the team? Curious to your thoughts. I am leaning that way for a project, but need to do some additional research. -
I will only be building database backed web apps w Lambda moving fwd personally so think that's a pretty serious endorsement. Typescript is fine. I'm sure it could help catch some bugs!
-
Are there any major gaps that are missing? I know you have the http://arc.codes project. Not sure where that comes in - haven't looked. I am imagining we will have a lot of APIs that just process JWT token for auth, then get/delete/save data or take some AWS service action
-
Yeah I didn't get that perscriptive on auth. It has session state so you can do JWT if you like them. We just use session variables. I'd be happy to do a 30min vid chat/demo of getting goin and what to look out for.
-
Yeah I would totally be game for that. I'll send you a DM and we'll go from there. Thanks!
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.