Operations
Ongoing management and governance are critical to ensuring that your Marketplace offerings remain accurate, secure, and valuable over time. Whether you are sharing data via Delta Sharing, exposing models, or delivering collaboration objects such as MCP servers, providers should treat Marketplace listings as living products, not one-time publishing events.
Operational lifecycle
Successful data products follow a continuous cycle:
- Publish - Create listings, configure shares, set up recipients
- Monitor - Track usage, watch for anomalies, measure adoption
- Maintain - Rotate tokens, update schemas, refresh sample notebooks
- Iterate - Respond to feedback, expand coverage, improve metadata
Key principles
- Treat data as a product - Versioning, documentation, and support matter as much as the data itself
- Automate what you can - Use Workflows and automation for refresh, alerting for anomalies, and system tables for tracking
- Plan for change - Schema evolution, recipient turnover, and access patterns will shift over time
- Own the cost model - Understand egress considerations and plan accordingly
In this section
| Topic | Description |
|---|---|
| Runbook | Change management, health checks, deprecation, and governance |
| Access management | Fulfillment workflows, revocation, and programmatic access |
| Monitoring | Alerts, dashboards, and operational queries |
| Workflow and automation | REST API, Python SDK, and automation scripts |
What's next
- Learn about sharing patterns for D2D and D2O
- Set up recipients and authentication
- Configure dynamic views for fine-grained access control
- Review listings for Marketplace best practices