Live data from Hacker News

List of Serverless Functions for JAMstack Apps

jamstackfns.com

1–10 of 25 posts

Re: List of Serverless Functions for JAMstack Apps

#2
Creator here, happy to answer any questions. Here's why I built this.

JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. Coined by Netlify's co-founder, JAMstack bridges the gap between static and dynamic websites. Capitalize on static site performance, security, and scalability while still having dynamic data.

I've seen this first-hand, building many JAMstacks sites myself. As a front-end developer, it was always challenging to find good examples of serverless functions. I'd usually have to dive through documentation, search StackOverflow, and ask questions on GitHub. They might have code but never had complete instructions for set up.

JAMstack Functions is a directory of the best serverless functions for JAMstack applications. Each function includes code for both Vercel (Next.js) and Netlify Functions, as well as instructions for setting up. Quickly deploy the function to your static site and start building.

Let me know which functions you'd like to see added.

Re: List of Serverless Functions for JAMstack Apps

#3
post #2

Creator here, happy to answer any questions. Here's why I built this. JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. Coined by Netlify's co-founder, JAMstack bridges the gap between static and dynamic websites. Capitalize on static site performance, security, and scalability while still having dynamic data. I've seen this first-hand, building many JAMstacks sites myself. As a front-end de…

>JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web.

How? "fundamentally reshaping the web" is a bold claim; how are those things reshaping the Web -- what's changing shape?

Re: List of Serverless Functions for JAMstack Apps

#4
Question for the frontend crowd: how have microservices/serverless aged over the past few years? I've largely avoided learning/using this type of architecture because intuitively it seems like a bad idea to split your app and business logic across a bunch of tiny services with unknown uptime stats (difficult to maintain, difficult to see macro view of your application, cascades of service dependencies, hard to onboard new people, etc). Are microservices and serverless architecture still considered a good idea? What are the benefits I'm not seeing?

Re: List of Serverless Functions for JAMstack Apps

#5
post #3
post #2

Creator here, happy to answer any questions. Here's why I built this. JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. Coined by Netlify's co-founder, JAMstack bridges the gap between static and dynamic websites. Capitalize on static site performance, security, and scalability while still having dynamic data. I've seen this first-hand, building many JAMstacks sites myself. As a front-end de…

>JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. How? "fundamentally reshaping the web" is a bold claim; how are those things reshaping the Web -- what's changing shape?

It's not, in my opinion.

Just something old - simple generated static site with sprinkle of {{currentJSFramework}}, a CDN, and some fancy marketing.

Re: List of Serverless Functions for JAMstack Apps

#6
post #3
post #2

Creator here, happy to answer any questions. Here's why I built this. JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. Coined by Netlify's co-founder, JAMstack bridges the gap between static and dynamic websites. Capitalize on static site performance, security, and scalability while still having dynamic data. I've seen this first-hand, building many JAMstacks sites myself. As a front-end de…

>JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. How? "fundamentally reshaping the web" is a bold claim; how are those things reshaping the Web -- what's changing shape?

Static sites have evolved. Today, they can handle real-time requests, process payments, manage customer accounts, and a lot more. Some other benefits:

  * Cheaper – Not making requests to the server on-demand
  * Faster – Served from a global CDN close to your users
  * Easier – No complicated deployments, better DX
How is this reshaping the web? In a way, we've come full circle. What's changing is how we get to a static site. JAMstack unlocks all the benefits of static sites with today's complex data requirements.

Re: List of Serverless Functions for JAMstack Apps

#7
post #5
post #3

Earlier quoted context omitted.

>JAMstack (JavaScript, APIs, and Markup) is fundamentally reshaping the web. How? "fundamentally reshaping the web" is a bold claim; how are those things reshaping the Web -- what's changing shape?

It's not, in my opinion. Just something old - simple generated static site with sprinkle of {{currentJSFramework}}, a CDN, and some fancy marketing.

What's your opinion on a more full-featured framework like RedwoodJS or Blitz then?

https://redwoodjs.com/ https://blitzjs.com/

Re: List of Serverless Functions for JAMstack Apps

#8

Question for the frontend crowd: how have microservices/serverless aged over the past few years? I've largely avoided learning/using this type of architecture because intuitively it seems like a bad idea to split your app and business logic across a bunch of tiny services with unknown uptime stats (difficult to maintain, difficult to see macro view of your application, cascades of service dependencies, hard to onboar…

It really depends on the scale of your organization. Microservices do have their place, but I'd argue that most of the time monoliths are fine.

Re: List of Serverless Functions for JAMstack Apps

#9
post #7
post #5

Earlier quoted context omitted.

It's not, in my opinion. Just something old - simple generated static site with sprinkle of {{currentJSFramework}}, a CDN, and some fancy marketing.

What's your opinion on a more full-featured framework like RedwoodJS or Blitz then? https://redwoodjs.com/ https://blitzjs.com/

So these are frameworks that generate static sites?

Re: List of Serverless Functions for JAMstack Apps

#10

Question for the frontend crowd: how have microservices/serverless aged over the past few years? I've largely avoided learning/using this type of architecture because intuitively it seems like a bad idea to split your app and business logic across a bunch of tiny services with unknown uptime stats (difficult to maintain, difficult to see macro view of your application, cascades of service dependencies, hard to onboar…

I'm not aware of a real "consensus," but a popular view (reflected by my experience) is that they're great for a large org with many teams working asynchronously (though they still introduce headaches), but that for most startups, the payoff is reduced greatly while the pain remains consistent.

You've probably around seen this, but DHH has a good piece on this in Signal v. Noise: https://m.signalvnoise.com/the-majestic-monolith/

Post reply on HN