Pengumpulan Koneksi Basis Data
Pelajari cara kumpulan koneksi menghilangkan beban pembukaan koneksi basis data untuk setiap permintaan, serta cara menentukan ukuran dan menyesuaikannya untuk kinerja.
Pengumpulan Koneksi Basis Data adalah pelajaran System Design Basics for Backend Developers gratis di CoddyKit. Ini adalah pelajaran 4 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar System Design Basics for Backend Developers, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus System Design Basics for Backend Developers mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
The Cost of a Connection
Opening a database connection is expensive: a TCP handshake, authentication, and session setup can take tens of milliseconds. Doing this on every request adds latency and load you do not need.
What a Connection Pool Is
A connection pool keeps a set of open connections ready to reuse. A request borrows one, runs its query, and returns it — no setup cost per request.
- Lower latency
- Less load on the database
- A natural cap on concurrent connections
Borrow and Return
The lifecycle is simple: acquire a connection, use it, release it back to the pool. The critical rule is to always release, even on error, or the pool leaks.
conn = pool.acquire()
try:
conn.execute('SELECT 1')
finally:
pool.release(conn)Pool Size Basics
The key tuning knob is the maximum pool size. Too small and requests queue waiting for a connection; too large and you overwhelm the database with concurrent work and context switching.
Sizing the Pool
Bigger is not better. A common starting heuristic is based on CPU cores, not request count, because the database can only do so much in parallel.
cores = 4
# A popular rule of thumb (HikariCP):
pool_size = (cores * 2) + 1
print('suggested pool size:', pool_size)Queueing and Timeouts
When all connections are busy, new borrowers wait. Set an acquisition timeout so a request fails fast instead of hanging forever when the pool is exhausted. Surfacing the error early is better than a silent stall.
Connection Leaks
A leak happens when a borrowed connection is never returned. The pool slowly drains until every request blocks. Always release in a finally block (or use a context manager / try-with-resources) and enable leak detection in production.
with pool.acquire() as conn:
conn.execute('SELECT 1')
# released automatically on exitIdle and Max Lifetime
Tune connection longevity: an idle timeout closes connections the pool no longer needs, and a max lifetime recycles old connections to dodge stale sockets and server-side timeouts (e.g. a firewall dropping idle TCP).
Pools and Horizontal Scaling
Watch the math: 20 app servers each with a 50-connection pool means up to 1000 connections hitting one database — likely over its limit. Size per-instance pools with the total fleet in mind, or add a connection proxy.
instances = 20
per_instance = 50
print('total connections:', instances * per_instance)External Poolers
Tools like PgBouncer sit between apps and the database, multiplexing many client connections onto a few database connections. They are essential when you have many app instances or serverless functions that each open connections.
Tuning by Measurement
Do not guess. Monitor pool metrics — active connections, wait time, timeouts — under realistic load, then adjust size and timeouts. The right pool size is the smallest one that keeps wait time near zero.
Quick Check
Test your understanding of connection pooling.
Recap
You learned to optimize database access with pooling:
- Pools reuse connections to avoid per-request setup cost
- Size pools by capacity (e.g. cores), not request volume
- Always release; guard against leaks with timeouts and detection
- Account for total connections across all instances; use poolers like PgBouncer at scale
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pengumpulan Koneksi Basis Data” gratis?
Ya — teks lengkap “Pengumpulan Koneksi Basis Data” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus System Design Basics for Backend Developers, upgrade ke CoddyKit PRO. Kursus System Design Basics for Backend Developers mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pengumpulan Koneksi Basis Data”?
Pelajari cara kumpulan koneksi menghilangkan beban pembukaan koneksi basis data untuk setiap permintaan, serta cara menentukan ukuran dan menyesuaikannya untuk kinerja. Kamu berlatih System Design Basics for Backend Developers dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai System Design Basics for Backend Developers?
Tidak diperlukan pengalaman sebelumnya. System Design Basics for Backend Developers di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 4 dari 4.
Berapa lama pelajaran “Pengumpulan Koneksi Basis Data” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran System Design Basics for Backend Developers ini?
Ya. Setiap pelajaran System Design Basics for Backend Developers menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Optimalisasi Latensi dan Laju Pemrosesan
- Konkurensi dan Paralelisme
- Pengujian dan Pembuatan Profil Performa
- Pengumpulan Koneksi Basis Data