IT Glossary
What is NoSQL?
The family of databases that step outside strict tables — documents, key-value stores, graphs — trading guarantees for flexibility and scale.
Classic relational databases keep the world in strict tables — defined columns, rigorous relationships, guaranteed consistency — a model that has served accounting, inventory and orders impeccably for fifty years. NoSQL is the umbrella name for database families that stepped outside that mould, each built for a specific pain. Document stores such as MongoDB hold whole flexible objects without a fixed schema, useful when product catalogues or profiles vary by category. Key-value engines like Redis answer in microseconds and power caches and sessions. Graph databases make relationships themselves queryable — recommendations, fraud detection. Search engines such as Elasticsearch make free text findable instantly. The honest price of that flexibility: strict transactional consistency often relaxes, and 'schemaless' frequently means the schema lives unguarded in application code. For a company evaluating an architecture proposal, the sane default remains a relational core (PostgreSQL being the era's sensible pick) with NoSQL pieces added surgically where a concrete pain demands them. When a vendor proposes NoSQL as the sole foundation 'because it is modern', one test cuts through: what problem in our data does it solve better than PostgreSQL, and who guarantees the numbers in the financial reports?
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Each data type in its element
Flexible catalogues, lightning caches, full-text search, complex relationship queries — specialised engines beat forcing one model onto everything.
Horizontal scale by design
NoSQL families grew up distributed across many servers — large volumes and traffic are absorbed by adding machines, not rewriting software.
Structures that evolve quickly
Without a rigid schema, the new product attribute or profile field ships today rather than after a month-long planned migration.
Frequently asked questions
SQL or NoSQL for our application — the short answer?
Relational as the foundation, almost always: business records like customers, orders and money need the consistency and reporting strength of the relational world. NoSQL enters for targeted pains — Redis where cache speed matters, Elasticsearch where search is the product, document stores where structure genuinely varies. Mature systems combine them; it is rarely either-or.
What risks come with building entirely on NoSQL 'for flexibility'?
Three pains that surface at maturity: business reporting becomes acrobatics, relaxed consistency produces ugly edge cases exactly around money — totals that disagree, races between operations — and the unguarded 'schema in code' accumulates historical data variants nobody can read anymore. All manageable by teams who know the territory, which is exactly why 'why this choice?' is a mandatory proposal question.
MongoDB, Redis, Elasticsearch keep appearing in proposals — what does each do?
The most common trio: MongoDB is the generalist document store for flexible structures and fast development; Redis is the lightning-fast memory layer for caches, sessions and queues, usually beside the main database rather than replacing it; Elasticsearch is the search engine behind free-text queries, filters and suggestions in serious online stores. Seeing them alongside a solid relational core signals mature architecture; seeing them instead of one raises a question mark.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247