 |
VOOZH | about |
|
VOOZH | about |
When most people think of a database, they often envision the traditional relational database model that involves tables made up of rows and columns. While relational database management systems still handle the lion’s share of data on the internet, alternative data models have become more common in recent years as developers have sought workarounds to the relational model’s limitations. These non-relational database models, each with their own unique advantages, disadvantages, and use cases, have come to be categorized as NoSQL databases.
This article will introduce you to a few of the more commonly used NoSQL database models. It will weigh some of their strengths and disadvantages, as well as provide a few examples of database management systems and potential use cases for each.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
This curriculum introduces open-source cloud computing to a general audience along with the skills necessary to deploy applications and websites securely to the cloud.
Browse Series: 39 tutorials
Former Technical Writer at DigitalOcean. Focused on SysAdmin topics including Debian 11, Ubuntu 22.04, Ubuntu 20.04, Databases, SQL and PostgreSQL.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Thanks a lot, a great demystification of all these terms and the NoSQL wave.
MarkLogic should be also mentioned as a Document based NoSQL database.
Enterprise NoSQL for Dummies book is free for download as e-Book for 6 months. http://www.nosqlfordummies.com/
What non-SQL solution would you suggest as an experimental or low-cost alternative to establishing single views of an entity across multiple data sets absent an MDM solution?
3ks very much,but the link for ‘Understanding Databases’ is not right,could you fix it !
Very well explained.
I find that a GraphDB for changing relationship structures (i.e., with equivalence, containment, categorization, sequence, version, variance, and description relation types) between subjects (i.e., nodes, nouns, terms of: Locations, Endeavors, Performing Units, Functions, Activities, Resources, Abilities types) works very well in providing navigation to associated deep-document-structures such as the forms and documents as records of Lifecycle processes (e.g., value-chains, supply chains, dependency chains, portfolios, mission lifecycles, humanitarian lifecycles, sustainability lifecycles, emergency management, and operational resiliency management).
I have been able to work with metadata repositories (i.e., triple stores) and enterprise content management (ECM) systems (i.e., content stores with full metadata repository) to achieve this capability, but now will design, develop, and test a Graph/Document DB version that might approach the capabilities of the collaboration and social-network-enabled ECM products.
Thanks, O. S. Tezer, for your awesome review of the NoSQL database!
I’m not sure if pros outweigh a major con: SQL compliant databases allow for an easy transition to and from other SQL compliant databases, such as Tibero, Oracle, Microsoft SQL and IBM DB2.
Thanks a lot. I love this post. So, can I translate this post into korean on my personal blog?
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
