Skip to main content

Relational vs. No-Sql

  • Chapter
  • First Online:
Scalability Patterns
  • 1032 Accesses

Abstract

Quite contrary to what it sounds, No-Sql means Not Only Sql. So far in the book we have been assuming that the persistence layer is only relational database or a scaled-out version of it. Before we actually talk about the architecture using No-Sql databases, it’s worth understanding the differences and appreciating the different kinds of No-Sql databases out there and understanding the different strengths they bring to the table. No-Sql databases are of many different kinds. The name given to the entire category of databases is kind of unfair. In my personal experience, some very good architects have made the mistake of thinking of Relational and No-Sql databases as an either-or, which is not the best way to approach architecting systems of scale.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 19.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 29.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Chander Dhall

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Dhall, C. (2018). Relational vs. No-Sql. In: Scalability Patterns. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1073-4_5

Download citation

Publish with us

Policies and ethics