architecture

Explain MD-DDL architecture concepts and compare with Data Mesh and Data Fabric.

1|Updated Feb 7, 2026

Search Tags:#architecture #positioning #comparison #data products #md-ddl #data autonomy

Ready to run

npx skills add https://github.com/Semprini/md-ddl --skill architecture-semprini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Semprini/md-ddl/tree/main/agents/agent-architect/skills/architecture
Command: npx skills add https://github.com/Semprini/md-ddl --skill architecture-semprini

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users understand and articulate the core architectural philosophy behind MD-DDL, enabling them to position it effectively within their organizations and compare it against alternative approaches.

Core Features & Use Cases

Explain MD-DDL Architecture: Provides clear explanations of concepts like Data Autonomy, model-driven generation, and data products.
Position Against Alternatives: Facilitates comparisons with Data Mesh, Data Fabric, EDW, and other architectures.
Prepare Presentation Material: Assists in creating talking points, executive summaries, and comparison tables for stakeholders.
Use Case: An Enterprise Architect needs to present MD-DDL to a CIO. They use this Skill to generate an executive summary highlighting business value, trade-offs, and next steps, tailored for a non-technical audience.

Quick Start

Use the architecture skill to explain the concept of Data Products as architecture quantum.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the MD-DDL architectural philosophy and how does Data Autonomy work?▼

The MD-DDL architectural philosophy centers on Data Autonomy and model-driven generation to create self-sufficient data products. Data Autonomy works by empowering data assets to operate independently within the architecture, reducing centralized bottlenecks.

How does MD-DDL architecture compare to Data Mesh and Data Fabric frameworks?▼

Comparing MD-DDL architecture to Data Mesh and Data Fabric frameworks highlights distinct approaches to decentralized data management. MD-DDL emphasizes model-driven generation and data products as architecture quanta, contrasting with the federated governance of Data Mesh and the integrated layering of Data Fabric.

How do I prepare an executive summary on data product architecture for a CIO?▼

To prepare an executive summary on data product architecture for a CIO, use the Skill's Teach mode to generate tailored talking points. It translates the MD-DDL architectural philosophy into business value propositions, trade-offs, and next steps for non-technical stakeholders.

Can I use MD-DDL architecture to position data products against an Enterprise Data Warehouse?▼

You can use MD-DDL architecture to position data products against an Enterprise Data Warehouse (EDW) by contrasting decentralized data autonomy with centralized EDW repositories. The Skill facilitates structural comparisons to highlight specific architectural trade-offs and business advantages.

When should I not use a model-driven generation approach for data architecture?▼

A model-driven generation approach for data architecture may not suit contexts requiring highly bespoke, non-standard data pipelines outside the data products paradigm. If an organization relies heavily on unstructured data without clear architectural models, alternative frameworks may be more appropriate.