ChanServ changed the topic of #debian-malaysia to: Selamat datang ke #DEBIAN-MALAYSIA! | info: wiki.debian.org/LocalGroups/Debian-Malaysia | telegram: t.me/debianmalaysia | muaturun: tinyurl.com/debian-current @ tinyurl.com/debian-nonfree-with-firmware | Log: https://tinyurl.com/2wwhd6hz | Debian - Sistem Operasi Universal!
<RSSBot[mambangmatrixorg][m]> Debian micronews: Debian Installer Bookworm Alpha 1 release https://lists.debian.org/debian-devel-announce/2022/09/msg00004.html ( https://micronews.debian.org/2022/1663831114.html )
<debianmalaysia[m]> [telegram] <hollowaykeanho> Not long way. It was by design as postgres was a relic before container technology take its place. You won't get the full power of k9s (high avail+perf+varieties) but only high avail+varieties. In another word, you're wasting resources. Re-designing DB takes a lot of time where SurrealDB R&D... (full message at <https://matrix.org/_matrix/media/r0/download/matrix.org/gNsqlKdRWVaJCucFvfebRbqc>)
<debianmalaysia[m]> [telegram] <hollowaykeanho> If insisting on Posgres, It's better to split them up: Postgres as its own machine (and scale vertically), k9s for your app services on the other and access Postgres via internal network IP.
<debianmalaysia[m]> Postgres with docker is mainly for standardising setup and configs and that's about it. You can do those with scripts / package manager anyway so docker is overkill for the job.