dido:public:s_cli:05_contents:03_prt:08_basic_dido_objects:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:s_cli:05_contents:03_prt:08_basic_dido_objects:start [2021/08/17 14:00] murphy [A.1.2 Overview of Ethereum Blockchain Objects] |
dido:public:s_cli:05_contents:03_prt:08_basic_dido_objects:start [2022/02/03 15:00] (current) 157.90.182.28 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 36: | Line 36: | ||
| </figure> | </figure> | ||
| - | * <WRAP>//Keep in mind, Ethereum is the database, [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contracts|smart contracts]] are the data tables, and transactions from wallets are the rows in each table.//(( | + | * <WRAP>//Keep in mind, Ethereum is the database, [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contract|smart contracts]] are the data tables, and transactions from wallets are the rows in each table.//(( |
| Andrew Hong, | Andrew Hong, | ||
| Hands-On Tutorials, | Hands-On Tutorials, | ||
| Line 54: | Line 54: | ||
| )) and lend themselves to mapping to the relational model well. | )) and lend themselves to mapping to the relational model well. | ||
| - | The use of Google's [[dido:public:ra:xapend:xapend.a_glossary:b:big_query|BigQuery]] was designed for analyzing data on the order of billions of rows, using a [[dido:public:ra:xapend:xapend.a_glossary:s:sql]]-like syntax. It runs on the Google Cloud Storage infrastructure and can be accessed with a REST-oriented application program interface (API). | + | The use of Google's [[dido:public:ra:xapend:xapend.a_glossary:b:big_query|BigQuery]] was designed for analyzing data on the order of billions of rows, using a [[dido:public:ra:xapend:xapend.a_glossary:s:sql]]-like [[dido:public:ra:xapend:xapend.a_glossary:s:syntax|syntax]]. It runs on the Google Cloud Storage infrastructure and can be accessed with a REST-oriented application program interface (API). |
| Trying to understand and use [[dido:public:ra:xapend:xapend.a_glossary:b:big_query]] developers have been able to tab into the Ethereum [[dido:public:ra:xapend:xapend.a_glossary:d:dlt]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain]]) data using very close to standard SQL(( | Trying to understand and use [[dido:public:ra:xapend:xapend.a_glossary:b:big_query]] developers have been able to tab into the Ethereum [[dido:public:ra:xapend:xapend.a_glossary:d:dlt]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain]]) data using very close to standard SQL(( | ||
| Line 66: | Line 66: | ||
| Figure {{ref>EtlArch}} provides a high-level flow of converting Ethereum Blockchain data into Google's BigQuery and as a consequence accessible using SQL. In this workflow, an Ethereum Node is deployed within a [[dido:public:ra:xapend:xapend.a_glossary:c:container|container]] orchestrated by a Kubernetes Engine. there are two paths through the data flow: a Real-Time path and a Daily Path. | Figure {{ref>EtlArch}} provides a high-level flow of converting Ethereum Blockchain data into Google's BigQuery and as a consequence accessible using SQL. In this workflow, an Ethereum Node is deployed within a [[dido:public:ra:xapend:xapend.a_glossary:c:container|container]] orchestrated by a Kubernetes Engine. there are two paths through the data flow: a Real-Time path and a Daily Path. | ||
| - | * In the Daily Path, a snapshot of the blockchain data is exported once a day, converted to [[dido:public:ra:xapend:xapend.a_glossary:c:csv]] files, and then loaded into BigQuery where the data can be accessed using the BigQuery Console. | + | * In the Daily Path, a [[dido:public:ra:xapend:xapend.a_glossary:s:snapshot|snapshot]] of the blockchain data is exported once a day, converted to [[dido:public:ra:xapend:xapend.a_glossary:c:csv]] files, and then loaded into BigQuery where the data can be accessed using the BigQuery Console. |
| * In the Real-Time Path that has a lagtime delay to prevent orphaned blocks, the data is streamed to a publish/subscribe utility that can create either | * In the Real-Time Path that has a lagtime delay to prevent orphaned blocks, the data is streamed to a publish/subscribe utility that can create either | ||
| * An ETL Dataflow is loaded into BigQuery where data can be accessed using the BigQuery Console | * An ETL Dataflow is loaded into BigQuery where data can be accessed using the BigQuery Console | ||
dido/public/s_cli/05_contents/03_prt/08_basic_dido_objects/start.1629223201.txt.gz · Last modified: 2021/08/17 14:00 by murphy
