# database-centric architecture

> software architecture

**Wikidata**: [Q2860294](https://www.wikidata.org/wiki/Q2860294)  
**Wikipedia**: [English](https://en.wikipedia.org/wiki/Database-centric_architecture)  
**Source**: https://4ort.xyz/entity/database-centric-architecture

## Summary
Database-centric architecture is a software architecture where the database serves as the central organizing principle and primary means of data management. It emphasizes data as the core asset, with applications built around and accessing data through a centralized database system. This approach contrasts with traditional application-centric architectures where data is distributed across multiple systems.

## Key Facts
- Database-centric architecture is a subclass of software architecture, which encompasses high-level structures of software systems
- Also known as data-centric architecture, Architecture Centrée Sur Les Données, and Architecture centree sur les donnees
- Has a freebase ID of /m/03cj4yh for identification in knowledge graphs
- Wikipedia page exists in English, French, Kazakh (kaa), and Portuguese (pt) languages
- Described on Wikidata as "software architecture" with a sitelink count of 4
- Associated with Microsoft Academic ID 154240960 (though this service has been discontinued)

## FAQs
### Q: What is the main characteristic of database-centric architecture?
A: The main characteristic is that the database serves as the central organizing principle, with applications built around and accessing data through a centralized database system rather than distributed data storage.

### Q: How does database-centric architecture differ from traditional application-centric architecture?
A: Database-centric architecture centralizes data management in a single database system, while application-centric architecture distributes data across multiple systems with each application managing its own data.

### Q: What languages is information about database-centric architecture available in?
A: Information about database-centric architecture is available in English, French, Kazakh, and Portuguese on Wikipedia.

## Why It Matters
Database-centric architecture matters because it addresses the fundamental challenge of data management in modern software systems. By centralizing data in a single, well-structured database, it enables better data consistency, integrity, and accessibility across multiple applications. This approach reduces data redundancy, simplifies maintenance, and improves data quality by ensuring that all applications work with the same authoritative data source. In an era where data is increasingly recognized as a critical business asset, database-centric architecture provides a framework for treating data as a first-class citizen rather than an afterthought. It supports complex business processes that require data from multiple sources, enables better analytics and reporting capabilities, and facilitates data sharing and reuse across organizational boundaries. The architecture also aligns with modern trends toward data-driven decision making and business intelligence, making it particularly relevant for organizations seeking to leverage their data assets effectively.

## Notable For
- Centralizing data management as the core organizing principle of software systems
- Providing a framework for treating data as a first-class asset rather than application output
- Supporting multiple applications through a single, authoritative data source
- Enabling better data consistency and integrity across organizational systems
- Facilitating data sharing and reuse across different business processes and applications

## Body
### Core Principles
Database-centric architecture operates on the principle that data should be the central organizing element of software systems. Rather than building applications that generate and manage their own data independently, this architecture creates a unified data layer that serves as the foundation for all applications.

### Data Management Approach
The architecture emphasizes centralized data storage and management, where a single database system serves as the authoritative source of truth. This approach ensures data consistency across all applications and eliminates the redundancy that occurs when multiple systems maintain separate copies of the same data.

### Application Integration
Applications in a database-centric architecture are designed to work with the centralized data store rather than maintaining their own data structures. This creates a more cohesive ecosystem where applications can easily share data and business logic can be implemented at the data level rather than within individual applications.

### Benefits and Trade-offs
The primary benefits include improved data quality, reduced redundancy, simplified maintenance, and better support for complex business processes that span multiple applications. However, this approach can create potential bottlenecks and may require more sophisticated database management capabilities compared to distributed architectures.

### Relationship to Other Architectures
Database-centric architecture represents a middle ground between purely centralized mainframe architectures and fully distributed microservices architectures. It provides many benefits of centralization while still allowing for distributed application development and deployment.

## References

1. [OpenAlex](https://docs.openalex.org/download-snapshot/snapshot-data-format)