StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Serverless
  4. Serverless Task Processing
  5. AWS Lambda vs Heroku Postgres

AWS Lambda vs Heroku Postgres

OverviewDecisionsComparisonAlternatives

Overview

AWS Lambda
AWS Lambda
Stacks26.0K
Followers18.8K
Votes432
Heroku Postgres
Heroku Postgres
Stacks607
Followers314
Votes38

AWS Lambda vs Heroku Postgres: What are the differences?

Introduction

AWS Lambda and Heroku Postgres are both popular cloud-based services that provide different functionalities. Here are the key differences between AWS Lambda and Heroku Postgres:

  1. Deployment Model: AWS Lambda is a serverless computing platform where developers write and upload code, and the platform automatically provisions and manages the execution environment. On the other hand, Heroku Postgres is a cloud-based database service that serves as a fully managed PostgreSQL database. It provides a traditional deployment model where users need to provision and manage their database instances.

  2. Scalability: AWS Lambda automatically scales the application to handle incoming requests, running code in parallel across multiple servers if required. It can handle large numbers of concurrent requests without the need for manual scaling. Heroku Postgres, as a database service, can handle horizontal scaling but requires manual configuration and monitoring for scaling up the database instances.

  3. Billing: AWS Lambda pricing is based on the actual usage and execution time of the functions. Users are billed for the number of requests and the duration of code execution. On the other hand, Heroku Postgres pricing is based on the size and performance level of the provisioned database instances. Users pay for the allocated resources regardless of the actual usage.

  4. Functionality: AWS Lambda focuses on serverless execution of code, providing a platform to run event-driven functions in response to various triggers. It supports various programming languages and enables developers to build scalable and event-driven applications easily. Heroku Postgres, on the other hand, is a fully managed PostgreSQL database service. It provides a wide range of database functionalities and features, including data storage, retrieval, and manipulation.

  5. Vendor Lock-in: AWS Lambda is a service provided by Amazon Web Services (AWS), which means it is tightly integrated with other AWS services and can utilize the AWS ecosystem. This can lead to vendor lock-in, as migrating to another cloud provider can be complex. Heroku Postgres, although owned by Salesforce, can be used independently and can be easily migrated to other PostgreSQL-compatible database providers.

  6. Management and Administration: AWS Lambda provides a fully managed environment where AWS takes care of server maintenance, security, and other management aspects. Developers only need to focus on writing code and configuring triggers. Heroku Postgres, as a managed database service, handles many management tasks like backups, high availability, and database upgrades, but users still need to handle certain administrative tasks like schema design and indexing.

In Summary, AWS Lambda is a serverless computing platform that focuses on executing event-driven functions at scale, while Heroku Postgres is a managed PostgreSQL database service that provides a traditional deployment model for PostgreSQL applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on AWS Lambda, Heroku Postgres

Tim
Tim

CTO at Checkly Inc.

Sep 18, 2019

Needs adviceonHerokuHerokuAWS LambdaAWS Lambda

When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:

  • Developer Experience trumps everything.
  • AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
  • If you need geographic spread, AWS is lonely at the top.

The setup

Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:

  • Pure, uncut, self hosted Kubernetes — way too much complexity
  • Managed Kubernetes in various flavors — still too much complexity
  • Zeit — Maybe, but no Docker support
  • Elastic Beanstalk — Maybe, bit old but does the job
  • Heroku
  • Lambda

It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?

I chopped that question up into the following categories:

  • Developer Experience / DX 🤓
  • Ops Experience / OX 🐂 (?)
  • Cost 💵
  • Lock in 🔐

Read the full post linked below for all details

357k views357k
Comments
Mark
Mark

Nov 2, 2020

Needs adviceonMicrosoft AzureMicrosoft Azure

Need advice on what platform, systems and tools to use.

Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.

We are open to either build it on AWS or on Microsoft Azure.

Apologies if I'm leaving out some info. My first post. :) Thanks in advance!

133k views133k
Comments
Jorge
Jorge

Jan 15, 2020

Needs advice

Considering moving part of our PostgreSQL database infrastructure to the cloud, however, not quite sure between AWS, Heroku, Azure and Google cloud. Things to consider: The main reason is for backing up and centralize all our data in the cloud. With that in mind the main elements are: -Pricing for storage. -Small team. -No need for high throughput. -Support for docker swarm and Kubernetes.

51.8k views51.8k
Comments

Detailed Comparison

AWS Lambda
AWS Lambda
Heroku Postgres
Heroku Postgres

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management.

Extend other AWS services with custom logic;Build custom back-end services;Completely Automated Administration;Built-in Fault Tolerance;Automatic Scaling;Integrated Security Model;Bring Your Own Code;Pay Per Use;Flexible Resource Model
High Availability;Rollback;Dataclips;Automated Health Checks
Statistics
Stacks
26.0K
Stacks
607
Followers
18.8K
Followers
314
Votes
432
Votes
38
Pros & Cons
Pros
  • 129
    No infrastructure
  • 83
    Cheap
  • 70
    Quick
  • 59
    Stateless
  • 47
    No deploy, no server, great sleep
Cons
  • 7
    Cant execute ruby or go
  • 3
    Compute time limited
  • 1
    Can't execute PHP w/o significant effort
Pros
  • 29
    Easy to setup
  • 3
    Extremely reliable
  • 3
    Follower databases
  • 3
    Dataclips for sharing queries
Cons
  • 2
    Super expensive
Integrations
No integrations available
PostgreSQL
PostgreSQL
Heroku
Heroku

What are some alternatives to AWS Lambda, Heroku Postgres?

Azure Functions

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Google Cloud Run

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Amazon RDS for PostgreSQL

Amazon RDS for PostgreSQL

Amazon RDS manages complex and time-consuming administrative tasks such as PostgreSQL software installation and upgrades, storage management, replication for high availability and back-ups for disaster recovery. With just a few clicks in the AWS Management Console, you can deploy a PostgreSQL database with automatically configured database parameters for optimal performance. Amazon RDS for PostgreSQL database instances can be provisioned with either standard storage or Provisioned IOPS storage. Once provisioned, you can scale from 10GB to 3TB of storage and from 1,000 IOPS to 30,000 IOPS.

Serverless

Serverless

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.

Google Cloud Functions

Google Cloud Functions

Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

Knative

Knative

Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center

OpenFaaS

OpenFaaS

Serverless Functions Made Simple for Docker and Kubernetes

ElephantSQL

ElephantSQL

ElephantSQL hosts PostgreSQL on Amazon EC2 in multiple regions and availability zones. The servers are continuously transferring the Write-Ahead-Log (the transaction log) to S3 for maximum reliability.

Nuclio

Nuclio

nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.

Apache OpenWhisk

Apache OpenWhisk

OpenWhisk is an open source serverless platform. It is enterprise grade and accessible to all developers thanks to its superior programming model and tooling. It powers IBM Cloud Functions, Adobe I/O Runtime, Naver, Nimbella among others.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase