Dorcas  Ferry

Dorcas Ferry

1607652750

Serverless Functions, Netlify vs Vercel, and the Jamstack

Serverless Functions are an extremely useful tool in a developer’s toolbelt, especially in the Jamstack world. You can use Serverless Functions to solve (almost) any backend needs you have without deploying and maintaining a server yourself. Josh Cunningham from Auth0 joins to talk about Serverless Functions, Open Source, and the Jamstack.

  • 00:00 - Intro
  • 03:00 - Working in Open Source
  • 07:30 - Stream Setup
  • 09:00 - Auth0 and Serverless
  • 12:00 - Serverless in Vercel vs Netlify
  • 14:00 - Statelessness in Serverless Functions
  • 18:20 - Uses for Serverless Functions
  • 27:40 - Desk Setups App with Serverless
  • 32:40 - Authentication in the Jamstack
  • 41:00 - Next.js Image Component
  • 43:00 - Auth0 Marketplace

#serverless #netlify #jamstack #developer

What is GEEK

Buddha Community

Serverless Functions, Netlify vs Vercel, and the Jamstack
Dorcas  Ferry

Dorcas Ferry

1607652750

Serverless Functions, Netlify vs Vercel, and the Jamstack

Serverless Functions are an extremely useful tool in a developer’s toolbelt, especially in the Jamstack world. You can use Serverless Functions to solve (almost) any backend needs you have without deploying and maintaining a server yourself. Josh Cunningham from Auth0 joins to talk about Serverless Functions, Open Source, and the Jamstack.

  • 00:00 - Intro
  • 03:00 - Working in Open Source
  • 07:30 - Stream Setup
  • 09:00 - Auth0 and Serverless
  • 12:00 - Serverless in Vercel vs Netlify
  • 14:00 - Statelessness in Serverless Functions
  • 18:20 - Uses for Serverless Functions
  • 27:40 - Desk Setups App with Serverless
  • 32:40 - Authentication in the Jamstack
  • 41:00 - Next.js Image Component
  • 43:00 - Auth0 Marketplace

#serverless #netlify #jamstack #developer

How To Get Page Views From Google Analytics via a Netlify Serverless function

After getting my blog up and running I recently decided to add Google Analytics to it, to understand what content people were most interested in. At first this was amazing as I could see which blog posts were getting the most traction, but after a while it became a bit of a pain to log into

my Google Analytics dashboard when all I wanted was to quickly see the

page view count of a blog post.

Wouldn’t it be easier to just go to my site and see the page view count displayed on each blog post? It most certainly would, and so that’s what I set out to build. Since Google Analytics has a powerful API, all I really needed to do was call that API and retrieve my information, but ideally I wouldn’t want to be making that call directly from this blog as that would mean exposing my API key and any other sensitive information to anyone who knows hows how to press F12.

TL;DR Here is the GitHub repository for the serverless function that I wrote for retrieving Google Analytics page views.

Since this blog is setup to be completely free (aside from the domain name), leveraging Netlify for the hosting, Cloudinary for images and Ghost

for the content management system, I definitely wouldn’t want to pay

for running a back-end (especially one that was simply fetching stats

from Google Analytics). And that’s where Netlify functions come in.

Netlify has a very generous free plan that allows 125k function

executions and 100 hours execution time, a quota that this blog would

never reach within 1 month, and this seemed like a perfect fit for what I

needed.

#netlify #serverless #expressjs #google-analytics #software-development #serverless-top-story #automate-page-view-capturing #netlify-analytics-serverless

Vincent Lab

Vincent Lab

1605017502

The Difference Between Regular Functions and Arrow Functions in JavaScript

Other then the syntactical differences. The main difference is the way the this keyword behaves? In an arrow function, the this keyword remains the same throughout the life-cycle of the function and is always bound to the value of this in the closest non-arrow parent function. Arrow functions can never be constructor functions so they can never be invoked with the new keyword. And they can never have duplicate named parameters like a regular function not using strict mode.

Here are a few code examples to show you some of the differences
this.name = "Bob";

const person = {
name: “Jon”,

<span style="color: #008000">// Regular function</span>
func1: <span style="color: #0000ff">function</span> () {
    console.log(<span style="color: #0000ff">this</span>);
},

<span style="color: #008000">// Arrow function</span>
func2: () =&gt; {
    console.log(<span style="color: #0000ff">this</span>);
}

}

person.func1(); // Call the Regular function
// Output: {name:“Jon”, func1:[Function: func1], func2:[Function: func2]}

person.func2(); // Call the Arrow function
// Output: {name:“Bob”}

The new keyword with an arrow function
const person = (name) => console.log("Your name is " + name);
const bob = new person("Bob");
// Uncaught TypeError: person is not a constructor

If you want to see a visual presentation on the differences, then you can see the video below:

#arrow functions #javascript #regular functions #arrow functions vs normal functions #difference between functions and arrow functions

Matt  Towne

Matt Towne

1595396280

Netlify Serverless Functions with Netlify Dev

It’s never been easier to create Serverless Functions. With Netlify, you can create and deploy Serverless Functions in minutes! In this video, I’ll show you how to run your Netlify Serverless Functions locally using the Netlify CLI and Netlify Dev command.

#serverless #netlify #netlify dev

Christa  Stehr

Christa Stehr

1602681082

Overcoming Common Serverless Challenges with Mainframe CICS Programs

By this point most enterprises, including those running on legacy infrastructures, are familiar with the benefits of serverless computing:

  • Greater scalability
  • Faster development
  • More efficient deployment
  • Lower cost

The benefits of agility and cost reduction are especially relevant in the current macroeconomic environment when customer behavior is changing, end-user needs are difficult to predict, and development teams are under pressure to do more with less.

So serverless is a no-brainer, right?

Not exactly. Serverless might be relatively painless for a new generation of cloud-native software companies that grew up in a world of APIs and microservices, but it creates headaches for the many organizations that still rely heavily on legacy infrastructure.

In particular, enterprises running mainframe CICS programs are likely to encounter frustrating stumbling blocks on the path to launching Functions as a Service (FaaS). This population includes global enterprises that depend on CICS applications to effectively manage high-volume transactional processing requirements – particularly in the banking, financial services, and insurance industries.

These organizations stand to achieve time and cost savings through a modern approach to managing legacy infrastructure, as opposed to launching serverless applications on a brittle foundation. Here are three of the biggest obstacles they face and how to overcome them.

Challenge #1

Middleware that introduces complexity, technical debt, and latency. Many organizations looking to integrate CICS applications into a microservices or serverless architecture rely on middleware (e.g., an ESB or SOA) to access data from the underlying applications. This strategy introduces significant runtime performance challenges and creates what one bank’s chief architect referred to as a “lasagna architecture,” making DevOps impossible.

#serverless architecture #serverless functions #serverless benefits #mainframes #serverless api #serverless integration