Skip to main content
Full Stack Radio

112: Guillermo Rauch - Building Serverless Applications with Now

68 min episode · 2 min read
·
Guillermo Rauch

Episode

68 min

Read time

2 min

Topics

Startups, Leadership, Software Development

AI-Generated Summary

Key Takeaways

  • Serverless Architecture Model: Now functions as a CDN capable of executing code on demand, not just serving static files. Deploy via GitHub integration or CLI, and code automatically scales infinitely across edge locations without monitoring servers, configuring Apache, or SSH access to infrastructure.
  • Function Granularity Strategy: Structure applications with one serverless function per route instead of single Express server handling all routes. This prevents bottlenecks, enables independent scaling per endpoint, and keeps function size minimal. Next.js automatically splits pages into separate functions for optimal performance.
  • Database Proximity Rules: Deploy functions near databases, not users. Example: function in Sydney calling San Francisco database adds 250ms latency per query. Moving function to US East reduced response time three times. Physical distance between function and data source matters more than user proximity.
  • Stateless Constraints Benefits: Serverless functions cannot write to filesystem, forcing better architecture patterns. WordPress image uploads fail initially but switching to S3 plugin eliminates hard drive space monitoring, provides automatic backups, and prevents common outage scenarios from disk capacity issues.
  • Monolith Deployment Pattern: Deploy entire project as single unit using now command or git push, not individual microservices. All functions build together from shared codebase using open-source builders like now/node, now/php, now/go. Enables code sharing while maintaining independent function scalability and isolation.

What It Covers

Guillermo Rauch explains how Now deploys serverless applications using CDN-edge code execution, eliminating server management while maintaining PHP-like simplicity through automatic function isolation, multi-language support, and framework-agnostic deployment across global regions.

Key Questions Answered

  • Serverless Architecture Model: Now functions as a CDN capable of executing code on demand, not just serving static files. Deploy via GitHub integration or CLI, and code automatically scales infinitely across edge locations without monitoring servers, configuring Apache, or SSH access to infrastructure.
  • Function Granularity Strategy: Structure applications with one serverless function per route instead of single Express server handling all routes. This prevents bottlenecks, enables independent scaling per endpoint, and keeps function size minimal. Next.js automatically splits pages into separate functions for optimal performance.
  • Database Proximity Rules: Deploy functions near databases, not users. Example: function in Sydney calling San Francisco database adds 250ms latency per query. Moving function to US East reduced response time three times. Physical distance between function and data source matters more than user proximity.
  • Stateless Constraints Benefits: Serverless functions cannot write to filesystem, forcing better architecture patterns. WordPress image uploads fail initially but switching to S3 plugin eliminates hard drive space monitoring, provides automatic backups, and prevents common outage scenarios from disk capacity issues.
  • Monolith Deployment Pattern: Deploy entire project as single unit using now command or git push, not individual microservices. All functions build together from shared codebase using open-source builders like now/node, now/php, now/go. Enables code sharing while maintaining independent function scalability and isolation.

Notable Moment

Rauch demonstrates deploying a single project mixing Hugo static generation, Gatsby pages, and Node.js functions together. The builder system allows different languages and frameworks per route within one monolithic repository, maintaining developer productivity while achieving serverless scalability benefits without microservice complexity.

Know someone who'd find this useful?

Episode Transcript

In this episode of Fullstack Radio, I talked to Guillermo Rauch about building and deploying serverless applications with Nao. This is Fullstack Radio episode 112. Hey everyone. Welcome to another episode of the Fullstack Radio podcast. I'm your host Adam Wadden and today it's my pleasure to be speaking with Guillermo Rausch. How's it going, Guillermo? Great. Thanks for having me. So, for anyone who's not familiar with you, do you mind sort of briefly introducing yourself and talking a little bit about the sorts of things you work on? Sure. So my name is Guillermo Rausch. I'm on Twitter at twitter.com/rauch, grauchg. I started my career, thanks to open source, really. Very at a very young age, I was, like, hacking with Linux and all this, like, sort of fun stuff. But my sort of breakthrough moment, was two things. It's starting with open source, contributing to open source, learning from open source, and joining online communities of supportive individuals. Like, I would be I would hang out all the time in, like, IRC IRC channels and, all kinds of websites for, like, programming communities. That led, to me becoming very interested in, PHP, specifically, like, CMS and and forum software that was, like, sort of turnkey, like, PHP, BB, and WordPress, and so on. But then I became really, really interested in this idea of using JavaScript to create very real time experiences, experiences where the end user had a direct connection with your website or application. So I started using this framework called MooTools, that it sort of started around the time that, also jQuery got started in the era of script, Taccolos and prototype JS. That framework was, led to a lot of the, early ideas and, that made it into frameworks like React today. And it was, a lot of people that were involved in mood tools at the time are now working on Facebook or other, awesome, places where they crafted the JavaScript experiences of the day. Another way in which I was interested in, making snappy, like, fast interactions was serving the user with the data, in real time before they get to request it. So this idea of sort of eliminating the refresh button as a thing that people needed to click. So I created a framework called Socket IO, which made WebSockets a lot more accessible, just because it made it easier to use and also because it made it completely cross browser, cross platform and so on. So, yeah, my, my, bio is basically working on open source, but also making it a lot more accessible to a lot of people and creating the best developer tools. And that's what our company does today. So I started a company about three years ago called Zite that is behind the, React Springboard called Next JS that many have probably heard of. Mhmm. And we built the serverless infrastructure for deploying, frameworks like Next JS and create React app and Vue, but …

Get the full transcript (11,801 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Full Stack Radio transcripts →

You just read a 3-minute summary of a 65-minute episode.

Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • WordPress image uploads fail initially but switching to S3 plugin eliminates hard drive space monitoring, provides automatic backups, and prevents common outage scenarios from disk capacity issues.
  • Rauch demonstrates deploying a single project mixing Hugo static generation, Gatsby pages, and Node.js functions together.
  • Next.js automatically splits pages into separate functions for optimal performance.
  • Serverless functions cannot write to filesystem, forcing better architecture patterns. WordPress image uploads fail initially but switching to S3 plugin eliminates hard drive space monitoring.
  • NowBy guest
    Guillermo Rauch explains how Now deploys serverless applications using CDN-edge code execution, eliminating server management while maintaining PHP-like simplicity through automatic function isolation, multi-language support, and framework-agnostic deployment across global regions.
  • Structure applications with one serverless function per route instead of single Express server handling all routes.
  • Rauch demonstrates deploying a single project mixing Hugo static generation, Gatsby pages, and Node.js functions together.

company

More from Full Stack Radio

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Full Stack Radio.

Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime