🛰️Platform architecture
With the stack report, we bring together a handful of resource types to enable learning about de-centralised technology stacks.
The architecture of the stack report itself is not de-centralized, although it does plug into such systems to capture data and leverage its capabilities as an identity system.
Website front-end
The website is the core digital interface to read articles, navigate through charts, dashboards and underlying datasets. Designed to function as a data space allowing for exploration of data.
The front-end codebase includes modules for rendering articles, charts and dashboards.
Chart module
Custom chart component to visualize datasets from the dataset catalog. See the chart resource description for further details.
Article module
Renders markdown with the possibility to include custom <Chart /> elements:
<chart start_date="{YYYY-MM-DD}" end_date="{YYYY-MM-DD}" >
{chart-id}
</chart>custom html chart element which is converted to the previously mentioned chart module.
Identity system
Accounts on the Tezos blockchain are used as identity system to access the interpretation layer. Leveraging the SIWT library, a sign-up flow is implemented in the website including verification of ownership of the Interpretation Layer Access Card.
Data catalog
The data catalog is built out of two components. A database which captures the metadata of various datasets and object storage to store the datasets themselves. See the dataset resource description for more information.
Data pipelines
Multiple data pipelines and data scripts are running continuously to publish datasets to the data catalog with up to date data. Most of these pipelines rely on the tzkt indexer as an intermediary, querying its underlying postgres database for Tezos transaction data.
CMS
A content magement system is in place to publish the articles by the research team.
Social layer
Analysis, charts and data visualisations from the stack report are posted across a number of social networks:
Last updated