Doug Wilson
1 min readJul 22, 2024

--

Arrrrrgh

As a first step, how about choosing the appropriate tool for the job?

Point 1 ought to be "Are you storing semi-structured or unstructured data?".

If so, then document databases, as opposed to all/any NoSQL databases might be more appropriate.

If not, document databases are NOT the right choice for structured data, like business entity data. Ever. Regardless of how bitchin' they might be. Regardless of how well they shard. And regardless of how well you heard that they perform vs SQL databases.

Your point 3 "Simplicity" will eat you alive once you start writing and maintaining your own referential integrity code which many document databases omit. Why? Because storing crap data "at scale" isn't going to save you. And planning! Hah! Who needs it, Boomer? Am I right? Just let us get to coding!

I weep for the future.

BTW, I absolutely adore the guy whose 40 years of experience you just ignored in the comments.

"The impudence! The audacity! The un-mit-igated gall!" -- The Grinch

--

--

Doug Wilson
Doug Wilson

Written by Doug Wilson

Doug Wilson is an experienced software application architect, music lover, problem solver, former film/video editor, philologist, and father of four.

No responses yet