How to Choose the Right Database
-
[How to choose the right database](https://towardsdatascience.com/how-to-choose-the-right-database-afcf95541741)
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
[How to choose the right database](https://towardsdatascience.com/how-to-choose-the-right-database-afcf95541741)
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Quote:
Since each query is done on a table — the query execution time depends on the size of the table. This is a significant limitation that requires us to keep our tables relatively small and perform optimizations on our DB in order to scale. In relational DBs scaling is done by adding more computing power to the machine that holds your DB, this method is called ‘Vertical Scaling’.
:laugh: Clearly the author has never heard of indexing.
Latest Articles:
Proxy class for TypeScript/Intellisense DOM manipulation -
Quote:
Since each query is done on a table — the query execution time depends on the size of the table. This is a significant limitation that requires us to keep our tables relatively small and perform optimizations on our DB in order to scale. In relational DBs scaling is done by adding more computing power to the machine that holds your DB, this method is called ‘Vertical Scaling’.
:laugh: Clearly the author has never heard of indexing.
Latest Articles:
Proxy class for TypeScript/Intellisense DOM manipulationI must admit that the same sentence jumped out at me too when I first read it. I thought they may have been referring to something else, as that's exactly what indexes are for.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
Quote:
Since each query is done on a table — the query execution time depends on the size of the table. This is a significant limitation that requires us to keep our tables relatively small and perform optimizations on our DB in order to scale. In relational DBs scaling is done by adding more computing power to the machine that holds your DB, this method is called ‘Vertical Scaling’.
:laugh: Clearly the author has never heard of indexing.
Latest Articles:
Proxy class for TypeScript/Intellisense DOM manipulationIndexing, query optimizer, primary keys, foreign relationships, ... it's all so much 80-ies and 90-ies - when you had to deal with hundreds of millions of records and you were lucky if you had a server with a gig of RAM. One of the projects my company dealing with have a server pre-requisite for 256Gb!!! RAM (not a hard drive) - I guess it's because it was programmed by the guys that at some point lost their developer jobs and now writing articles like that one.
-
Indexing, query optimizer, primary keys, foreign relationships, ... it's all so much 80-ies and 90-ies - when you had to deal with hundreds of millions of records and you were lucky if you had a server with a gig of RAM. One of the projects my company dealing with have a server pre-requisite for 256Gb!!! RAM (not a hard drive) - I guess it's because it was programmed by the guys that at some point lost their developer jobs and now writing articles like that one.
I'm a fan of a game called "Oxygen not included"; for a long time, it included the name "pokeshell molt" for two different items. It may be new to the developers that humans need a "unique" name to differentiate between the two. If they named the same and show up in a list, then you can only make a choice by trial-and-error. One of the basics of databases when learning what a primary key is :D
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
[How to choose the right database](https://towardsdatascience.com/how-to-choose-the-right-database-afcf95541741)
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Marc's complaint is only #2 on my facepalm list. #1 is the cheatsheet at the end. It says to use any of several specialist NoSQL databases if you're doing the workload they're hyper-optimized for. So far so good, if a little bit obvious. But for anything else use either a relational DB or a generalist NoSQL DB (document) which is an absolute give up for the one case where someone with a minimally functioning brain would need to consider what the best option for their workload is. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt