Build Well-Documented and Authenticated APIs in Node.js with Fastify

engineering , Principal Developer Advocate

If you’re an API developer working with Node.js, then you’re probably familiar with Express. But have you tried out the Fastify framework to build with power, speed, and convenience? In this walkthrough, we build a full-featured, easy-to-consume API with Fastify. And we deploy it to the cloud with ease. We show you how to:

  • Get started working with Fastify to build an API
  • Implement API authentication by using a JSON web token (JWT)
  • Use Fastify’s Swagger plugins to generate an OpenAPI specification
  • Consume the OpenAPI specification with Postman, giving you an API client that can send requests seamlessly to your back-end API
  • Deploy your application to Heroku

Building a GPT Backed by a Heroku-Deployed API

engineering , Principal Developer Advocate

How to connect your GPT on OpenAI to a backend Node.js app

Late in 2023, OpenAI introduced GPTs, a way for developers to build customized versions of ChatGPT that can bundle in specialized knowledge, follow preset instructions, or perform actions like reaching out to external APIs. As more and more businesses and individuals use ChatGPT, developers are racing to build powerful GPTs to ride the wave of ChatGPT adoption.

Working with ChatGPT Functions on Heroku

engineering , Principal Developer Advocate

How to Build and Deploy a Node.js App That Uses OpenAI’s APIs

Near the end of 2023, ChatGPT announced that it had 100M weekly users. That’s a massive base of users who want to take advantage of the convenience and power of intelligent question answering with natural language.

ChatGPT Interface

With this level of popularity for ChatGPT, it’s no wonder that software developers are joining the ChatGPT app gold rush, building tools on top of OpenAI’s APIs. Building and deploying a GenAI-based app is quite easy to do—and we’re going to show you how!

Let's Debug a Node.js Application

engineering , Principal Developer Advocate

There are always challenges when it comes to debugging applications. Node.js' asynchronous workflows add an extra layer of complexity to this arduous process. Although there have been some updates made to the V8 engine in order to easily access asynchronous stack traces, most of the time, we just get errors on the main thread of our applications, which makes debugging a little bit difficult. As well, when our Node.js applications crash, we usually need to rely on some complicated CLI tooling to analyze the core dumps.

Let It Crash: Best Practices for Handling Node.js Errors on Shutdown

engineering , Principal Developer Advocate

This blog post is adapted from a talk given by Julián Duque at NodeConf EU 2019 titled "Let it crash!."

Before coming to Heroku, I did some consulting work as a Node.js solutions architect. My job was to visit various companies and make sure that they were successful in designing production-ready Node applications. Unfortunately, I witnessed many different problems when it came to error handling, especially on process shutdown. When an error occurred, there was often not enough visibility on why it happened, a lack of logging details, and bouts of downtime as applications attempted to recover from crashes.

Julián: Okay. So, as Brian said, my name is Julián Duque, it will be...

Subscribe to the full-text RSS feed for Julián Duque.