loading...
Cover image for JAMstack Roundup for October 23rd 2019
TakeShape

JAMstack Roundup for October 23rd 2019

navinmoney profile image Navin Mani Originally published at takeshape.io ・2 min read

Here are 5 great videos and articles we're bringing you this week!

  1. Static First: Pre-Generated JAMstack Sites with Serverless Rendering as a Fallback
    One of the principles of JAMstack is that of pre-rendering. If we are going to pre-generate our sites ahead of time, how do we make them feel dynamic? How do we work with things like user generated content? πŸ€”

  2. 5 Frontend Podcasts - here's what I listen to to stay up to date
    I love listening to podcasts. Whenever I've got a moment, while commuting, going to work or cooking, I'm just putting on my headphones. I would like to share with you my favorite ones. 🎧

  3. I created the exact same app in React and Vue. Here are the differences.
    Having used Vue at work, I had a fairly solid understanding of it. I was, however, curious to know what the grass was like on the other side of the fence β€” the grass in this scenario being React. πŸ‚

  4. Building a serverless SMS sender in 10 minutes
    A web based SMS sender can be a very handy tool any developer out there, which can be used for a wide range of use cases. In this article, we will build one. πŸ“²

  5. Learn GraphQL using JavaScript and Apollo
    This video tutorial teaches why you should use GraphQL and explains concepts such as schema and resolvers. We will construct a simple API that supports hello world but we will also show how we can integrate with an external API. πŸ“½

Posted on by:

navinmoney profile

Navin Mani

@navinmoney

Navigating cutting edge technology, and writing about it

TakeShape

TakeShape is Headless GraphQL CMS.

Discussion

markdown guide
 

Great articles! JAM stack is something I have been messing with recently.

It is interesting to see the first article generates a new build for every submission. In the end they talk about running scheduled jobs to scale better. This would take the load off the server to SSR every individual request. The bundling of requests to build all at once would take a decent amount of processing power, I would assume.

Though, I love this is experiment. I definitely would love to delve in to the cost-benefit of having an infrastructure like this.