5 ms·
There are specific cases where a non SQL database is better. Chances are if you haven't hit problems you can't solve with an SQL database you should be using an
by xupybd 6y ago
There are specific cases where a non SQL database is better. Chances are if you haven't hit problems you can't solve with an SQL database you should be using an SQL database. Postgres is amazing and free why would you use anything else.
- maccard 6y agoPeople keep saying there are specific cases where NoSQL is better, but never what any of those cases are.
- throwaway870923 6y agoTime series is one. Consider an application with 1000 time series, 1 hosts, and 1000 RPS. You are trivially looking at 1M writes per second per host. This usually requires something more than "[just] using a RDBMS".
- kfir 6y agoHere you go, this is from a system I helped building 10 years ago that is an eternity in tech - https://qconlondon.com/london-2010/qconlondon.com/dl/qcon-london-2010/slides/GeirMagnusson_ProjectVoldemortAtGiltGroupeWhenFailureIsntAnOption.pdf https://qconlondon.com/london-2010/qconlondon.com/dl/qcon-lo...
- kfir 6y agoa bit more context: High-velocity transactional systems (e.g any e-commerce store with millions of users all trying to shop at the same time), I helped to build such a 10 years ago here is the presentation - https://qconlondon.com/london-2010/qconlondon.com/dl/qcon-london-2010/slides/GeirMagnusson_ProjectVoldemortAtGiltGroupeWhenFailureIsntAnOption.pdf https://qconlondon.com/london-2010/qconlondon.com/dl/qcon-lo...