Platform architecture
Last updated
Last updated
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.
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.
Custom chart component to visualize datasets from the dataset catalog. See the c resource description for further details.
Renders markdown with the possibility to include custom <Chart /> elements:
custom html chart element which is converted to the previously mentioned chart module.
Accounts on the blockchain are used as identity system to access the . Leveraging the SIWT library, a sign-up flow is implemented in the website including verification of ownership of the Interpretation Layer Access Card.
A content magement system is in place to publish the articles by the research team.
Analysis, charts and data visualisations from the stack report are posted across a number of social networks:
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 resource description for more information.
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 as an intermediary, querying its underlying postgres database for Tezos transaction data.