Then repmgr for managing replication and barman for backups.
The stack is nice because keepalived gives you a virtual ip that you point your apps to, then you can promote a standby to primary (or have one auto promote on a failure) and the VIP will flip to the new primary. All in all you get like 5-10 seconds of “down” time when it flips (depending on how aggressive or conservative you want to be with the rise and fall settings).
Edit: caveat you won’t get keepalived to work if you are using AWS and spread your Postgres servers across AZ’s, they would have to be in the same AZ.
Edit 2: You can simplify the setup if you don’t need connection pooling, in that case skip pgbouncer.
We need to stop applying terms like “think” to AI and computers. Computers don’t “think”, they process, that is all. Comparing, or calling, a CPU to the “brain” is also extremely problematic, CPUs in reality are nothing like a biological brain.
That said, it’s impressive that a computer can process enough data to output an any sort of engine.
Publicly routable is wonderful. My first job was a company that happened to have somehow acquired a class B, so all our computers just had normal real addresses, they always had the same address whether you were on a VPN or a home network or whatever and remoting into the company network just worked.
Why? It neatly separates concerns. Routing and reachability should be handled by the network. The upper layers should handle authorization and discovery.
Public IPs also definitely don't need to be accessible from the wide Internet. Border firewalls are still a thing.
I have noticed this too. I suspect as HN grew, it caught the attention of bad actors that want to drive a particular narrative and they actively run campaigns that utilize both paid shills and bots.
> So given this pattern, I don't feel like the domain name is something relevant for most end users.
Oh but it is, even if the user doesn’t realize it. How are you going to do SSL without a domain name? I don’t know of any provider that is trusted by a major browser, that will issue ssl certs for an ip instead of a domain name. You could use your own CA but no browser will accept it, and your visitors will be greeted with a browser warning.
These aren’t really new rules, there is nothing to be be “grandfathered” into. Maybe they made some slight adjustments but I was looking at the process to become a registrar 5+ years ago and the process as I recall was pretty much the same.
Keepalived -> pgbouncer -> postgresql
Then repmgr for managing replication and barman for backups.
The stack is nice because keepalived gives you a virtual ip that you point your apps to, then you can promote a standby to primary (or have one auto promote on a failure) and the VIP will flip to the new primary. All in all you get like 5-10 seconds of “down” time when it flips (depending on how aggressive or conservative you want to be with the rise and fall settings).
Edit: caveat you won’t get keepalived to work if you are using AWS and spread your Postgres servers across AZ’s, they would have to be in the same AZ.
Edit 2: You can simplify the setup if you don’t need connection pooling, in that case skip pgbouncer.