“A reporting component diagram with a reporting portal, schedule component and report catalog calling a report API. The API uses a query builder, which reads through a data warehouse adapter and sends results to a report renderer. The renderer uses export and email-delivery components.”
Read the decisions behind it.
Supports interactive and scheduled reports.
Isolates warehouse access behind an adapter.
Separates rendering from export and email delivery.
Use this diagram to explain the main component responsibilities in a reporting platform.
Other examples in this family.
Common questions
Why use a warehouse adapter?
It keeps report logic independent from the connection details of the underlying data warehouse.
What does the report renderer own?
It turns queried data into a report format and hands it to delivery components.
Can scheduled and interactive reports share an API?
Yes. They can be different entry points that invoke the same reporting workflow.