Scaling the GitLab database

Re:Scaling the GitLab database by YorickPeterse on Monday October 30, 2017 @06:24PM (#15589504)

Yes, you can typically push PostgreSQL very far while still using a fairly simple setup (e.g. no sharding). Unfortunately too many times people have this mindset that a slow application is the result of a slow/bad database (as in "it's an RDBMS and RDBMS' don't scale"), and not the result of it being misused (e.g. badly written queries, lack of proper indexes, that sort of thing). At GitLab it took quite a while to get everybody to see this.

[ Parent | on HN ]

Re:Scaling the GitLab database by awj on Monday October 30, 2017 @07:43PM (#15590013)

1. Write web application with little to no idea how an RDBMS works

2. Run into inevitable performance problems

3. Decide that your database is at fault, rewrite in NoSQL

4. Buy into NoSQL hype, push 5x resources on your NoSQL solution

5. Profit?

There are NoSQL options that are great for lots of things. It takes some significant expertise to know if your thing is one of those things. Expertise you probably don't have if you don't even have a moderately deep knowledge of RDBMS-es.

[ Parent | on HN ]

Re:Scaling the GitLab database by YorickPeterse on Monday October 30, 2017 @08:38PM (#15590275)

    > Buy into NoSQL hype, push 5x resources on your NoSQL solution

NoSQL is so last year, NewSQL is the future!

[ Parent | on HN ]

Re:Scaling the GitLab database by philliphaydon on Monday October 30, 2017 @09:38PM (#15590538)

Lack of indexes vs way too many indexes that writes suffer.

[ Parent | on HN ]