, 20 tweets, 7 min read Read on Twitter
"Scared serverless: what we learned after quitting servers for a year" - James Beswick (@jbesw) #ServerlessDaysBOS
consultancy companies that builds web/mobile apps. After building so many of those found each had a separate stack, similar technologies, reused code. There was an inability to scale and if MVPs succeed, needed to rewrite to scale #ServerlessDaysBOS
Also while things were getting real time and slick, and customers didn't accept clunky apps #ServerlessDaysBOS
First impression of serverless - you can resize images, and that's it? Turns out no, you can build whole apps! #ServerlessDaysBOS
The app design workflow changed! First started with lambda as a monolith and lift and shift into the lambda that connects directly to RDS. Wasn't actually serverless #ServerlessDaysBOS
Stuck a REST API gateway connected to the lambda with the business logic, connected to dynamo DB, with a vue frontend. And it was better #ServerlessDaysBOS
First, get tools right; next burn down the middle layer; use SPA framework; use and love DynamoDB; use serverless framework or SAM; and outsource your auth #ServerlessDaysBOS
Auth is hard to get right and has no benefits to getting right, but it's a horror show if it goes wrong, so outsource your auth #ServerlessDaysBOS
Learning how to do serverless correctly is painful, and the industry is struggling through it. We went from building monoliths to rube-goldberg machines #ServerlessDaysBOS
But serverless isn't a rube-goldberg machine, it's more like lego. You need to stick them together but once they're connected it's pretty stable #ServerlessDaysBOS
Think big while using serverless - test for scale, plan for latency. You have the ability to test whatever on it! #ServerlessDaysBOS
Even though lambda allows up to 15 minutes now, you should still have seconds-long functions in general. Also be stateless (even though state between invocations is cool to look at, it's not good in a real app) #ServerlessDaysBOS
If you can flowchart, you can serverless! #ServerlessDaysBOS
Think about minimum viable change when changing serverless system, and optimize where you change #ServerlessDaysBOS
Easy to outsource the problems you don't want to focus on - can easily integrate small work units. More granular security allows easier auditing and smaller blast radius of issues. #ServerlessDaysBOS
Not everything in the system needs to be serverless to see benefits. Start with the small low hanging fruit like cron jobs just to get developers used to the workflow and the mindset #ServerlessDaysBOS
Serverless agility is one of the greatest benefits. Can have major scope changes that lead to minor code changes #ServerlessDaysBOS
Many of the technical limitations of serverless are melting away (longer durations, serverless DB's SQS as a trigger, etc) #ServerlessDaysBOS
The issues these days: there's growing time-gaps in orgs. The tech in their orgs can be 50 years old. And there's social fear of change and people are scared their jobs are going away #ServerlessDaysBOS
After a year of serverless - they discovered it actually works (to the shock of all of them). It is still new, and often you come up with the solution instead of looking it up #ServerlessDaysBOS
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Ann Guilinger
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!