Database – Definition, Use Cases and Best Practices at a Glance
Organised collection of data that can be stored and queried electronically. Relational databases use tables; NoSQL uses flexible models.
What is a Database? SQL, NoSQL & Types Explained
Databases are the memory of every application. Customer data, orders, sensor readings or chat history – everything is stored, organised and queried in databases.
Choosing the right database is one of the most important architecture decisions and affects performance, scalability and cost for the life of the application.
This glossary entry for Database gives you a clear Definition, practical Use Cases and Best Practices at a glance – with examples, pros and cons, and FAQs.
What is Database?
- Database – Organised collection of data that can be stored and queried electronically. Relational databases use tables; NoSQL uses flexible models.
A database is an organised system for storing, managing and querying data electronically. A DBMS (Database Management System) is the software that runs database operations.
Relational databases (RDBMS) like PostgreSQL, MySQL and SQL Server store data in tables with rows and columns linked by relationships (foreign keys). SQL is the standard query language.
NoSQL databases like MongoDB (document), Redis (key-value), Cassandra (wide-column) and Neo4j (graph) use flexible models for specific use cases. NewSQL (e.g. CockroachDB) combines SQL with horizontal scaling.
How does Database work?
A relational database stores data in normalised tables (e.g. customers, orders, products) linked by foreign keys. SQL (SELECT, INSERT, UPDATE, DELETE) reads and changes data. Transactions (ACID) ensure consistency. Indexes speed up queries. ORMs (Prisma, TypeORM, SQLAlchemy) abstract SQL in code.
Replication distributes data across servers for resilience and read performance.
Practical Examples
PostgreSQL for SaaS: Multi-tenant with row-level security, JSON for flexible structures and full-text search.
MongoDB for content: Flexible documents for different content types (articles, videos, podcasts) without a fixed schema.
Redis for caching: Cache for frequently read data (sessions, API responses) – response time from milliseconds to microseconds.
Neo4j for recommendations: Graph database for relationships between users, products and purchases – basis for recommendation engines.
Typical Use Cases
Web apps: PostgreSQL or MySQL for users, content and business data
E-commerce: Catalogue, orders, customers and inventory
Analytics: Data warehouses (BigQuery, Redshift) for BI and reporting
Real-time: Redis and MongoDB for chat, scores and IoT data
Search: Elasticsearch or Meilisearch for full-text and faceted search
Advantages and Disadvantages
Advantages
- Integrity: ACID in relational DBs keeps data consistent
- SQL: Universal query language with decades of use
- Scaling: Replication, sharding and managed services enable horizontal scale
- Flexibility: NoSQL fits varied structures and access patterns
- Managed: Cloud (AWS RDS, Supabase, PlanetScale) handles operations and backup
Disadvantages
- Schema: Relational DBs need migrations when structure changes
- Scaling limits: Vertical scaling hits hardware limits; horizontal is complex
- ORM overhead: Abstractions can lead to inefficient queries (e.g. N+1)
- Operations: Self-hosted DBs need backup, monitoring, updates and tuning
Frequently Asked Questions about Database
PostgreSQL or MySQL?
PostgreSQL: better SQL compliance, JSON, arrays, full-text search and advanced features (CTEs, window functions). MySQL: easier to set up, fast for simple read workloads, widely used (WordPress, Laravel). For new projects PostgreSQL is often recommended for flexibility and features. Both are available as managed services.
When SQL and when NoSQL?
SQL when: data is structured and relational, transactions matter (finance, e-commerce), you need complex JOINs. NoSQL when: schema must be flexible (CMS, IoT), you need horizontal scale, or simple access patterns with real-time performance. Many systems use both: SQL for business data, Redis for cache, Elasticsearch for search.
What does a database cost?
Self-hosted: free (PostgreSQL, MySQL are open source) plus server cost. Managed: Supabase from €0 (free tier), AWS RDS from ~€15/month, PlanetScale from ~$29/month. Enterprise (MongoDB Atlas, Aurora, etc.) €50–500/month depending on size. For many startups a free tier or small managed instance is enough.
Direct next steps
If you want to apply or evaluate Database in a real project, start with these transactional pages:
Database in the Context of Modern IT Projects
What this glossary entry gives you
This page gives a concise definition of Database. You also get practical use cases and best practices at a glance.
You can use it to evaluate the technology for your next project. Database sits in the domain of Basics. It plays a significant role across many IT projects.
Look beyond isolated technical merits
When you judge whether Database is the right fit, look beyond isolated technical merits. You should weigh the full project context.
Consider the following factors:
- Existing team expertise
- Current infrastructure
- Long-term maintainability
- Total cost of ownership (TCO)
Drawing on our experience from over 250 software projects, we have found that correctly positioning a technology or methodology within the broader project context often matters more than its isolated strengths.
How we help you decide
At Groenewold IT Solutions, we have worked with Database across multiple client engagements. We know its advantages and the typical challenges during adoption.
If you are unsure whether Database suits your requirements, ask us for an honest, no-obligation assessment. We analyze your situation. We recommend the approach that delivers the most value. We may suggest an alternative solution if that fits better.
Where to go next
For more terms in Basics and related topics, open our IT Glossary.
For concrete applications, costs and processes, use our service pages and topic pages. There you will see many of the concepts from this entry applied in practice.
Related Terms
Want to use Database in your project?
We are happy to advise you on Database and find the optimal solution for your requirements. Benefit from our experience across over 200 projects.