• Pricing
© 2026 Serverless, Inc. All rights reserved.

Framework

  • Overview
  • Documentation
  • Plugins360
  • Pricing

Learn

  • Blog
  • GuidesUpdated
  • Examples240
  • Courses

Resources

  • Support
  • Security
  • Trust Center
  • Status

Community

  • Slack
  • GitHub47k
  • Forum
  • Meetups

Company

  • About
  • Careers
  • Contact
  • Partners

Legal

  • Terms of Service
  • Privacy Policy
  • Trademark
  • DMCA
theburningmonk

Serverless + lambda protobuf responses

by

Demo using API Gateway and Lambda with Protocol Buffer

  1. Serverless + lambda protobuf responses

lambda-protobuf-demo

Demo using API Gateway and Lambda with Protocol Buffer.

In this demo you'll find 3 handlers:

  • json - always return response in JSON
  • proto - always return response in protocol buffer format, you need to set the Accept header to application/x-protobuf for this to work otherwise API Gateway just returns the base64 string instead
  • contentNegotiated - uses the Accept header to decide whether to return JSON or protocol buffer, and return 406 Not Acceptable if the Accept header is neither application/json nor application/x-protobuf

For more details, please read this blog post.

Deployment

If you're on Linux, run ./deploy.sh.

If you're not on Linux, run docker-compose up.

Why use docker for deployment? Because the protobufjs library used to encode Protocol Buffer messages has a dependency that is distributed as a native binary. So in order to get the right version you need to run grab the dependency on a Linux system, docker provides a nice abstraction to do that.

Contents

  • lambda-protobuf-demo
  • Deployment

Related

GuidesPluginsExamplesSlack CommunitySupport