Conversation I had with colleague whose contract was ending and was trying to get a Data Architecture job elsewhere.
- Colleague: Hey I took an interview for Data Architecture. Can you please help answer me some questions.
- Me: Of-course.
- Colleague: What is top-down (or) bottom-up approach?
- Me: Before we go into the questions, can you tell me what Data Architecture means to you?
- Colleague: Modeling database tables which are normalized and constrains are added at the DB level to be able to maintain data integrity.
- Me: Nice. That defines data modeling. What about Data Architecture?
- Colleague: Ha?????
Data Architecture is composed of models, policies, rules or standards that govern which data is collected, and how it is stored, arranged, integrated, and put to use in data systems and in organizations
Wikipedia
It can be further be broken down into
- Implementation of Information Management Reference Architecture
- OLTP
- OLAP
- DWH
- Data Lakes
- Data Modeling: Is the act of exploring data-oriented structures. It is the analysis of data objects and their relationships to other data objects.
- Master Data Management: Is a technology-enabled discipline in which business and IT work together to ensure the uniformity, accuracy, stewardship, semantic consistency and accountability of the enterprise’s official shared master data assets.
- Reference Data Management: Is an oversight of data that define the set of permissible values to be used by other data fields. Reference data gain in value when they are widely re-used and widely referenced
- Metadata Management: Is the oversight of data associated with data assets to ensure that information can be integrated, accessed, shared, linked, analyzed and maintained to best effect across an organization