With Google’s graveyard[1] growing so fast, I’m careful with new Google announcements. An API like this sounds particularly problematic to replace sometime in future. [1]: https://killedbygoogle.com/. - Source: Hacker News / 5 days ago

Number 293 of killed things by Google: https://killedbygoogle.com/. - Source: Hacker News / 6 days ago

Submit search to https://killedbygoogle.com/ ? - Source: Hacker News / 24 days ago

No way. Related dead Google products: - Nest Secure - Google Home Max If it's not about ads, Google will kill it. [1] https://killedbygoogle.com/. - Source: Hacker News / 25 days ago

> Google is large enough to not care about small opportunities. It ends up focusing on bigger opportunities that result in shittier products overall. For example, just a few months ago they cut 17 features from Google Assistant because they couldn't monetize them, sorry, because these were "small opportunities": https://techcrunch.com/2024/01/11/google-is-removing-17-underutilized-assistant-features/ > all are... - Source: Hacker News / 26 days ago

I have also a spark cluster created with google cloud dataproc. Source: about 1 year ago

Specifically, we heavily rely on managed services from our cloud provider, Google Cloud Platform (GCP), for hosting our data in managed databases like BigTable and Spanner. For data transformations, we initially heavily relied on DataProc - a managed service from Google to manage a Spark cluster. - Source: dev.to / about 2 years ago

With that, the best way to maximize processing and minimize time is to use Dataflow or Dataproc depending on your needs. These systems are highly parallel and clustered, which allows for much larger processing pipelines that execute quickly. Source: over 2 years ago