4 ms·
It is very frustrating to work with engineers who don't understand the nuances of RDBMS and assume they can solve all the things. The small company I work for
by VirusNewbie 4y ago
It is very frustrating to work with engineers who don't understand the nuances of RDBMS and assume they can solve all the things. The small company I work for has 3B rows. We have a high write volume. Can you use an RDBMs database to solve this? Sure, but it would be a terrible waste of engineering effort.
- qaq 4y ago? as opposed to buggy reimplementation of subset of RDBMS functionality on the Application side?
- mulmen 4y agoIs that hard? Sounds like it might be a little expensive in terms of server resources but I don’t see why the engineering would be hard. I’m curious how you handle this with less engineering effort without using an RDBMS.
- HelloNurse 4y agoA "high write volume" requires fast disks, and billions of rows require large disks. Two simple requirements that are the same for any relational or less relational database. What's interesting is query performance, and a RDBMS supports explicit control over indexing (usually including analyzing execution plans to find out which queries are going to work well). Where do you see "a terrible waste of engineering effort"?