Team integration and data governance¶

Tinybird supports a wide range of industries and products. Customers organize themselves and their businesses in different ways, but there are overarching principles you can adopt and adapt. Knowing how to integrate your team with Tinybird is important to get the most value out of the platform.

Before you start¶

You need to be familiar with the following core Tinybird concepts:

Roles and responsibilities¶

Tinybird allows you to share Data Sources across Workspaces. This means you can create Workspaces that map your organization, and not have to duplicate the Data Sources. In general, most Tinybird users have an ingestion Workspace where the owners of the data ingest the data, clean the data, and prepare it for onward consumption. They then share these Data Sources with other internal teams using the Sharing Data Sources feature.

You can have as many ingestion Workspaces as you need: bigger organizations group their Workspaces by domain, some organizations group them by team. For instance, in a bank, you might find different teams managing their own data and therefore several ingestion Workspaces where data is curated and exposed to other teams. In this case, each team maps to a domain:

However, in other companies where data is centralized and managed by the data platform, you might find a single ingestion Workspace where all the data is ingested and shared with other onward Workspaces where specific domain users build their own use cases:

Some organizations rely on a hybrid solution, where data is provided by the data platform but each domain group also ingest their own data:

Whatever your approach, it's an established pattern to have an ingestion or data-platform Workspace or team who own ingestion and data preparation, and share the desired Data Sources with other teams. These downstream, domain-specific teams then create the Pipe logic specific to their own area, usually in a Workspace specifically for that domain. That way, the responsibilities reflect a manageable, clear separation of concerns.

Enforcing data governance¶

Tinybird supports your data governance efforts in the following ways:

• Availability is assured by the platform's uptime SLA. Tinybird wants all your teams to be able to access all the data they need, any time they need. You can monitor availability using monitoring tools, which includes monitoring ingestion, API Endpoints, and quarantined rows. Tinybird offers a straightforward way to reingest quarantined rows and maintain Materialized Views to automatically reingest data.

• Control over data access is managed through a single Organization page in Tinybird. You can enforce the principle of least privilege by assigning different roles to Workspace members, and easily check data quality and consumption using Tinybird's Service Data Sources. Tinybird also supports schema evolution and you can keep multiple schema versions running at the same time so consumers can adjust at their own pace.

• Usability is maximized by having ingestion Workspaces. They allow you to share cleaned, curated data, with specific and adjusted schemas giving consumers precisely what they need. Workspace members have the flexibility to create as many Workspaces as they need, and use the Playground feature to sandbox new ideas.

• Consistency: Data owners have responsibility over what they want to share with others. You can monitor which Workspace is ingesting data.

• Data integrity and quality, especially at scale and at speed, is essential. Just like availability, it's a use case for leveraging Tinybird's monitoring capabilities. See Additional ecosystem tools. Ingestion teams can build Pipes to monitor everything about their inbound data and create alerts. Alerts can be technical or business-related.

• Data security: This information is available at the top-level Organizations page and also in individual Workspaces.

Additional ecosystem tools¶

Tinybird is built around the idea of data that changes or grows continuously, and provides the following tools as part of Tinybird. These tools help you get insights on and monitor your Workspaces, data, and resources.

Operations log¶

The Operations log shows information on each individual Data Source, including its size, the number of rows, the number of rows in the quarantine Data Source (if any), and when it was last updated.

The Operations log contains details of the events for the Data Source, which are displayed as the results of the query. Use it to see every single call made to the system (API call, ingestion, jobs). This is helpful if you're concerned about one specific Data Source and need to investigate.

Monitoring¶

You can use the Organizations feature for managing Workspaces and Members, and monitoring their entire consolidated Tinybird consumption in one place.

For example, you can track costs and usage for each individual Workspace.

Testing¶

To ensure that all production load is efficient and accurate, all Tinybird API Endpoints that you create in your Workspaces can be tested before going to production. You can do this by using version control.

Alerts and health checks¶

To ensure everything is working as expected once you're in production, any team can create alerts and health checks on top of Tinybird's Service Data Sources.

Next steps¶

• Watch this video to understand how Factorial sets domain boundaries and organizes their teams.
• Build something fast and fun - follow the quick start tutorial.