Get started
Your own data

Google BigQuery and MedAppz

Your Own Database streams your records into a BigQuery table in your own Google Cloud project, partitioned by day. It works today with a service-account key from that project.

LiveEverywhere MedAppz is offered
What it does

What happens through Google BigQuery

  • Creates the table on first use with a fixed schema: event_id, stream, event_type, aggregate_type, aggregate_id, occurred_at and a JSON payload.
  • Partitions the table by day on occurred_at unless you ask for otherwise.
  • Uses the event id as BigQuery’s insertId, so a retried batch is not stored twice.
  • Holds its place and marks the connection failed if the service account cannot sign in.
Switching it on

What it takes

  1. Step 1Create a dataset and a service account allowed to write to it.
  2. Step 2Paste the service-account JSON key in API Keys, under Your own database.
  3. Step 3Add a BigQuery connection in Your Own Database and pick the streams.

What it does not do yet

BigQuery’s de-duplication only covers a short window, so delivery is still at least once.
In the store

The apps that use Google BigQuery

Each carries its status from the catalog.

Your Own Database · live in clinics
Questions

Asked about this connection

Does MedAppz connect to Google BigQuery?
Yes. It works on medappz.com today. Your Own Database streams your records into a BigQuery table in your own Google Cloud project, partitioned by day. It works today with a service-account key from that project.
How do I switch on Google BigQuery?
Create a dataset and a service account allowed to write to it. Paste the service-account JSON key in API Keys, under Your own database. Add a BigQuery connection in Your Own Database and pick the streams.
What does the Google BigQuery connection not do yet?
BigQuery’s de-duplication only covers a short window, so delivery is still at least once.
Related

Read next