Serverless Limitations

Syntax - Tasty Web Development Treats

Wes Bos

Tech News, News, Technology

4.9 • 1.2K Ratings

🗓️ 28 November 2022

⏱️ 20 minutes

🔗️ Recording | iTunes | RSS

🧾️ Download transcript

Summary

In this episode of Syntax, Wes and Scott talk through some of the limitations of using serverless in your project. Sentry - Sponsor If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up. MagicBell - Sponsor MagicBell is the the notification inbox for your product. Add a MagicBell to your product for announcements, billing, workflow, and other notifications. The free plan supports up to 100 Monthly Active Users - use the coupon code SYNTAXFM for 10% off the first 12 months. Show Notes 00:23 Welcome 01:08 Sponsor: Sentry 01:59 Sponsor: MagicBell 03:11 Topic introduction 04:44 Function limit Puppeteer 08:51 Node support 10:00 Cron jobs 11:12 Local development Miniflare 11:45 Database access SQLite 12:42 Sharing code 13:07 Environmental variables Netlify environmental variables 14:37 Timeouts 15:47 Sass is expensive 17:26 Infastructure as code 19:02 Search Algolia Shameless Plugs Scott: LevelUp Tutorials Wes: Wes Bos Tutorials Tweet us your tasty treats Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets

Transcript

Click on a timestamp to play from that location

0:00.0	Monday! Monday! Monday! Open wide dev fans! Get ready! To stuff your face with
0:07.0	JavaScript CSS! Node modules! Barbecue tips! Get workflow! Break dancing! Soft skills!
0:12.0	Web development! The hastiest! The craziest! The tastiest! Web development
0:16.0	treats! Coming in hot! Here is Wes! Barakuda! Boss! And Scott!
0:22.0	Tell Toro Lungo! Tolinsky!
0:27.0	Welcome to syntax on this Monday hasty treat. We're going to be pushing it to the limit.
0:34.0	And I'm talking about the limit of serverless. We're going to be talking about serverless
0:38.0	limitations in some situations, maybe where serverless has changed how you work.
0:45.0	Not things you can't get around, but maybe some things to be aware of.
0:49.0	My name is Scott Tolinsky. I'm a developer from Denver. With me, as always, is Wes Boss.
0:54.0	Hey, everybody. Hey, Wes, how's it going, man? That's going good. I'm just
0:58.0	talking about serverless limitations. Yeah, serverless limitations. And we're
1:03.0	going to be a sponsor by two amazing companies that have absolutely zero limitations.
1:07.0	I'm talking about Century and Magic Bell. Century is the perfect place to log and
1:11.0	capture all of your errors and exceptions and keep track of what's going on in your
1:15.0	location and any given point. Whether that's the UI, the API, the app, anything you
1:20.0	could possibly imagine, you can collect all of that information, log it into
1:24.0	Century, see how many people it's affecting, see what kind of reach this thing has,
1:29.0	also see when this was introduced. Maybe this was introduced in a specific
1:32.0	version. Maybe it was introduced by a specific person. You can go ahead and create
1:38.0	GitHub issues directly from Century. You can see performance metrics for your
1:42.0	application to see how fast it's performing. And overall, this is one of those
	...

Please login to see the full transcript.

Previous episode | Next episode

Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.