Checklist progress
0/168Learned
Heroku Architect
Study Checklist
Checklist progress
0/168Learned
Demonstrate knowledge of Heroku Postgres, including data handling, security, and common use cases for follower databases. Describe the use cases of Dataclips.
0/18
What is the difference between a Heroku Postgres fork and a Heroku Postgres follower?
Learn this conceptWhen should a Heroku Postgres fork versus a follower be used?
Learn this conceptHow does PgBouncer (connection pooling) address Heroku Postgres connection exhaustion?
Learn this conceptHow does Heroku Postgres handle encryption at rest and in transit?
Learn this conceptWhat compliance scenarios does Heroku Postgres encryption address?
Learn this conceptArchitect solutions using Apache Kafka on Heroku to facilitate streaming communication between applications, services, or functions.
0/8
Architect solutions using Heroku Key-Value Store
0/9
Demonstrate the ability to prescribe a third-party add-on and add-on sharing, when appropriate.
0/5
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Heroku Architect studiers.
PgBouncer is a connection pooler that sits between application clients and Heroku Postgres, sharing a limited set of server-side database connections among many client connections. It prevents connection exhaustion—and the resulting Out of Memory errors and queuing—by keeping server connections open and reusing them across clients rather than creating a new process per connection. Heroku offers PgBouncer in two deployment models: server-side (managed, transaction-pooling only) and client-side (dyno buildpack, configurable).