3 Big Announcements from Google

Summary

Google Cloud announces three significant updates: BigQuery subscription in Google Pub/Sub, general availability of Google BigLake, and expansion of the Cloud Healthcare API to four additional regions.

Abstract

Google Cloud has recently announced three major updates that will benefit data engineers and data scientists. The first update is the introduction of BigQuery subscription in Google Pub/Sub, which simplifies data integration by allowing direct writing from Cloud Pub/Sub to BigQuery. The second update is the general availability of Google BigLake, which eliminates the need for data duplication and supports data governance by assigning rights to data. Lastly, the Cloud Healthcare API is now available in four additional regions, providing a managed solution for storing and accessing healthcare data in the Google Cloud. These updates not only simplify tasks but also potentially save costs.

Bullet points

Google Cloud announces three significant updates for data engineers and data scientists.
The first update is the introduction of BigQuery subscription in Google Pub/Sub, which simplifies data integration.
The second update is the general availability of Google BigLake, which eliminates the need for data duplication and supports data governance.
The third update is the expansion of the Cloud Healthcare API to four additional regions, providing a managed solution for storing and accessing healthcare data in the Google Cloud.
These updates simplify tasks and potentially save costs.

Update 1: BigQuery subscription in Google Pub/Sub

With the new subscription you can write directly from Cloud Pub/Sub to BigQuery. Pub/Sub is used for streaming analytics and data integration pipelines to ingest and distribute data. This method is as effective as messaging-oriented middleware for service integration or as a queue to parallelize tasks. If you are using data from mainly streaming data from one source to the SaaS Data Warehouse BigQuery, in this case Google’s Pub/Sub, you may have used solutions like Cloud Functions, Data Flow or Data Prep as another intermediary. So you don’t have to write your own pipelines for data ingestion from Pub/Sub into BigQuery. This makes data integration way more easy now [1]. Read more about it here.

Update 2: Google made BigLake generally available now

Indeed, you may already be using it but with the label being generally available now, you are sure that it will stay and you can design your IT infrastructure without any risk [2]. If you want to know how to use the BigLake, feel free to click here. It’s a big benefit that you don’t have to duplicate your data in two different environments and create data silos. You can also support your data governance because with BigLake you can also assign rights to the data.

Google BigLake — Source: THENEXTPLATFORM

Update 3: The Cloud Healthcare API is now available in 4 additional Regions

Google now allows more customers to use the Cloud Healthcare API, namely

asia-southeast2 (Jakarta)

us-east1 (South Carolina)

us-west1 (Oregon)

us-west3 (Salt Lake City)

providing a managed solution for storing and accessing healthcare data in the Google Cloud. It’s a useful tool to bridge between existing care systems and applications hosted on Google Cloud [1]. This could be an interesting option, especially for many healthcare operations, to combine their old world with the new analytics and Data Science capabilities of the Google Cloud.

So again some interesting improvements in the Google Cloud especially for the Data Engineers and Data Scientists among us. Not only that the updates simplify certain tasks, but also possibly help to save you some money.

3 Big Announcements from Google

Great Updates regarding Google Cloud and BigQuery

Update 1: BigQuery subscription in Google Pub/Sub

Update 2: Google made BigLake generally available now

Update 3: The Cloud Healthcare API is now available in 4 additional Regions

Sources and Further Readings