[HN Gopher] Show HN: List of Serverless Functions for JAMstack Apps
___________________________________________________________________
Show HN: List of Serverless Functions for JAMstack Apps
Author : leerob
Score : 16 points
Date : 2020-04-28 20:41 UTC (2 hours ago)
(HTM) web link (jamstackfns.com)
(TXT) w3m dump (jamstackfns.com)
| testbot123 wrote:
| 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?
| leerob wrote:
| 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.
| finestkludge wrote:
| 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/
| leerob wrote:
| 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.
| benatkin wrote:
| JAMstack is a nonsensical term. LAMP is a stack. It's Linux,
| Apache, MySQL, and PHP. JAM at most is a kind of stack, and an
| extremely vague one.
| Nicksil wrote:
| >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?
| winrid wrote:
| It's not, in my opinion.
|
| Just something old - simple generated static site with
| sprinkle of {{currentJSFramework}}, a CDN, and some fancy
| marketing.
| leerob wrote:
| What's your opinion on a more full-featured framework like
| RedwoodJS or Blitz then?
|
| https://redwoodjs.com/ https://blitzjs.com/
| winrid wrote:
| So these are frameworks that generate static sites?
| leerob wrote:
| Yes.
| leerob wrote:
| 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.
___________________________________________________________________
(page generated 2020-04-28 23:00 UTC)