[HN Gopher] Lessons Learned from 5 Years of Scaling PostgreSQL
       ___________________________________________________________________
        
       Lessons Learned from 5 Years of Scaling PostgreSQL
        
       Author : jwilm
       Score  : 28 points
       Date   : 2021-04-15 19:31 UTC (3 hours ago)
        
 (HTM) web link (onesignal.com)
 (TXT) w3m dump (onesignal.com)
        
       | tkiolp4 wrote:
       | I'm planning to use Postgres for my next Saas, But all these
       | "issues" worry me. I have used MySQL in the past and, even though
       | my web services don't handle too many connections/transactions,
       | MySQL always perform good. I've seen other articles regarding
       | Postgres issues when it comes to scaling. I've come to realize
       | that I like MySQL when it comes to performance, but I don't like
       | it when it comes to semantics and design... hence my attempt to
       | switch to Postgres.
        
         | jwilm wrote:
         | Both RDBMS have good performance. Lots of the issues we ran
         | into really are related to scale. If you know that your data
         | set will never be particularly large, most of these issues will
         | not come up. Other issues like managing replicas, promotions,
         | etc. will be shared between RDBMS.
         | 
         | One of the nice things about PostgreSQL regardless of scale are
         | the tools they provide for optimizing your application. EXPLAIN
         | and EXPLAIN ANALYZE are really powerful tools for figuring out
         | _why_ a query performs badly and validating that indexing you
         | add actually improved query performance.
        
           | NoThisIsMe wrote:
           | PostgreSQL is great but lots of DBs (MySQL included) have
           | EXPLAIN/ANALYZE
        
         | tyingq wrote:
         | Maybe balance your reading with other articles that talk about
         | how well plain old vertical scaling (bigger box) works these
         | days. You can fit 128 cores, huge amount of memory, and 24+
         | NVME drives into a 2U rack spot these days and not have to
         | worry much about sharding, horizontal scaling, etc, for quite
         | some time.
        
         | blacktriangle wrote:
         | This particular company is data-intensive and scaled up to
         | 75TB.
         | 
         | Quick back of the number calculation for a pretty boring B2B
         | CRUD app, at 75TB of data we'd have more income than the GDP of
         | Earth. YMMV.
        
       ___________________________________________________________________
       (page generated 2021-04-15 23:02 UTC)