desktop VS pgbouncer

On the desktop platform end, we’re making progress on the diagnostics project and preparing for the Desktop 5.2 release.

On the desktop platform end, we’re in extremely hardcore negotiation with Apple to ship v5.2.1 of our desktop app to the Mac app store. While flexing that muscle, we’re also working on the desktop diagnostics UI. While not technically platform work: floating panels for Calls are coming to the desktop app, adding to the list of differentiators that make the desktop app The Best Client™️ for every extremely hardcore Mattermost user. And if you’re not one of them, you have no business being here, frankly.

On the desktop platform end, we are finally getting native node_modules to work, allowing for deeper integration into each of the OSes we support. As an initial demo of this ability, we will support picking up the “do not disturb” mode from the OS. On recruitment news, we will have the desktop team double in size on August 8, when Tasos will join us 🎉 Which is, incidentally, the same day that Pantelis will join as the web and desktop engineering lead (again: 🎉). That’s right, we’re onboarding half of Greece in a single day (the other half was already working for us in the SRE team).

On the desktop platform end, translations have landed! If you know some language that is not English, join our localization channel and help out getting the desktop app translated to your favorite and least favorite languages! There’s also work in progress to improve window resizing performance. The resizing performance regressed to be comically slow on some OSes, as you can see in my jiff attached to that PR.

On the desktop platform end, we’re making good progress on our goal to add translations to the desktop app, as well as adding native node_module support. We’re also ramping up on how to do e2e test runs in an automated fashion.

Went ahead and posted a feature request: https://github.com/mattermost/desktop/issues/1476

Thanks to MongoDB drivers all consistently providing connection monitoring and pooling functionality, external connection pooling solutions aren't required (ex: Pgpool, PgBouncer). This allows applications built using MongoDB drivers to be resilient and scalable out of the box, but based on what we understand regarding the number of connections applications establish to MongoDB clusters it stands to reason that at a certain point as our application deployments increase, so will our connections.

Pgbouncer - resolvia o problema do limite de conexões no postgres. Mas a API “saudável” manteve o número de conexões baixo o suficiente.

Pgbouncer maintainer here. Overall I think this is a great description of the tradeoffs that PgBouncer brings and how to work around/manage them. I'm actively working on fixing quite a few of the issues in this blog though

1. Named protocol-level prepared statements in transaction mode has a PR that's pretty close to being merged: https://github.com/pgbouncer/pgbouncer/pull/845

A common solution is connection pooling. Supabase currently offers pgbouncer which is single-threaded, making it difficult to scale. We've seen some novel ways to scale pgbouncer, but we have a few other goals in mind for our platform.

Great observation! :)

We worked upstream to have `search_path` properly handled (tracked per client) by pgbouncer.

https://github.com/pgbouncer/pgbouncer/commit/8c18fc4d213ad4...

Check config.md in that commit for a verbose, humanized description.