378 karma · joined July 25, 2012
On your note about resiliency and scale - its always a waste of money until shit hits the fan. Then you really pay for it.
I've ran into an integer PK being almost exhausted in values twice now. In one of these cases I used pg-osc to rewrite a 8TB table on disk without downtime over a period of a week to fix the issue. In the other case it was about 6TB within 2 days. Its doable, but the amount of planning and time it takes is non-trivial.
I so far have no found any other viable solutions either. I keep hearing about logical replication but I haven't seen a great real-world solution at scale so far.
And Google is trying to push their identity products, but they are very far from being mature enough for enterprise needs.
I generally suspect folks making comments like this are really not familiar with the products and their uses.
And what a lot of people seem to realize is that there are reasons for this, the controls exist for a reason. Allowing everyone access is not necessarily a good thing across the board. That realization will at some point be forced though, which leads into regulation in some form, which will takes us full circle again...
My own personal theory is that because the barrier of entry is so low, people get a little too excited about being a contributor and solving a problem "differently" (sometimes before even understanding the problem space well enough). In short - lot of it is inexperience.
Something like puma-dev does this pretty painlessly out of the box too. Running a container just for that seems frankly overkill.