Use it when you want to begin cloud architecture work without writing the first draft from scratch.
Data Mesh on Cloud AI Prompt
Design a data mesh architecture on this cloud platform. Organization size: {{org_size}} Domains identified: {{domains}} (finance, product, marketing, operations, etc.) Cloud pro... Copy this prompt template, run it in your AI tool, and use related prompts to continue the workflow.
Design a data mesh architecture on this cloud platform.
Organization size: {{org_size}}
Domains identified: {{domains}} (finance, product, marketing, operations, etc.)
Cloud provider: {{provider}}
Current state: {{current_state}} (centralized data warehouse, fragmented silos, etc.)
1. Data mesh principles:
- Domain ownership: each business domain owns and publishes its own data products
- Data as a product: data is treated with product-quality standards (SLA, documentation, quality)
- Self-serve data platform: a platform team provides the infrastructure; domain teams use it
- Federated computational governance: global policies enforced automatically; local flexibility
2. Domain data product structure:
Each domain publishes:
- Input data: raw data from its systems
- Transformed data: cleansed, enriched, domain-specific tables
- Output data products: interfaces for other domains (S3 path, Snowflake share, BigQuery authorized dataset)
- SLA: freshness, availability, schema stability guarantees
- Documentation: data catalog entry with owner, description, quality metrics
3. Technical implementation on AWS:
- Account per domain: separate AWS accounts for finance, product, marketing data
- Cross-domain access: AWS Lake Formation data sharing; S3 bucket policies for cross-account access
- Central catalog: AWS Glue Data Catalog federated with domain-level catalogs
- Self-serve platform: reusable Terraform modules for each domain to provision standard infrastructure
4. Governance layer:
- Global policies (applied everywhere): PII tagging, retention rules, access logging
- Domain policies (domain-specific): schema standards, SLA definitions, quality thresholds
- Policy engine: AWS SCP (service control policies), OPA (Open Policy Agent), Apache Ranger
5. Data product contract:
interface_type: s3_parquet
location: s3://finance-data-products/revenue/v1/
schema: {order_id: bigint, amount_usd: numeric, date: date}
sla_freshness: 4 hours
owner: finance-analytics@company.com
version: 1.2.0
Return: domain architecture, AWS/GCP/Azure implementation approach, governance layer design, and data product contract schema.When to use this prompt
Use it when you want a more consistent structure for AI output across projects or datasets.
Use it when you want prompt-driven work to turn into a reusable notebook or repeatable workflow later.
Use it when you want a clear next step into adjacent prompts in Cloud Architecture or the wider Cloud Data Engineer library.
What the AI should return
The AI should return a structured result that covers the main requested outputs, such as Data mesh principles:, Domain ownership: each business domain owns and publishes its own data products, Data as a product: data is treated with product-quality standards (SLA, documentation, quality). The final answer should stay clear, actionable, and easy to review inside a cloud architecture workflow for cloud data engineer work.
How to use this prompt
Open your data context
Load your dataset, notebook, or working environment so the AI can operate on the actual project context.
Copy the prompt text
Use the copy button above and paste the prompt into the AI assistant or prompt input area.
Review the output critically
Check whether the result matches your data, assumptions, and desired format before moving on.
Chain into the next prompt
Once you have the first result, continue deeper with related prompts in Cloud Architecture.
Frequently asked questions
What does the Data Mesh on Cloud prompt do?+
It gives you a structured cloud architecture starting point for cloud data engineer work and helps you move faster without starting from a blank page.
Who is this prompt for?+
It is designed for cloud data engineer workflows and marked as advanced, so it works well as a guided starting point for that level of experience.
What type of prompt is this?+
Data Mesh on Cloud is a single prompt. You can copy it as-is, adapt it, or use it as one step inside a larger workflow.
Can I use this outside MLJAR Studio?+
Yes. The prompt text works in other AI tools too, but MLJAR Studio is the best fit when you want local execution, visible Python code, and reusable notebooks.
What should I open next?+
Natural next steps from here are Cloud Data Platform Architecture, ELT vs ETL on Cloud, Full Cloud Data Engineering Chain.