Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Should You Avoid Distributed Database Systems?

DZone's Guide to

Should You Avoid Distributed Database Systems?

· Java Zone ·
Free Resource

Verify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!

A recent post from Mark Perham's blog titled "The Emperor has no Clothes" suggests that distributed database systems may not be as useful as many believe them to be. Perham's opinion, in fact, is very concise:

My belief is simple: avoid distributed databases if possible. You will pay a heavy tax for their use. 

However, his argument doesn't come without defense, and his qualification of "if possible" is key. There are scenarios, which Perham lays out, in which it is beneficial or even necessary to use distributed databases, but there are also many in which a more "old-fashioned" database such as SQL may be completely adequate, or even superior.

Is there too much hype surrounding distributed databases? The argument brings to mind the recent criticism in Big Data of a perceived obsession with using Hadoop for everything (every dataset may not call for it), but the reality of network failures is a serious issue, and it is important to take precautions.

What do you think? Does Perham have a point, or is there more to the story when it comes to distributed databases? Leave us a comment and let us know.


Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}