Google Cloud's official blog, with product announcements and engineering guidance on GCP, Kubernetes, Anthos, and machine learning.
HN commenters link it as a source for Google's product announcements and best practices, such as graceful pod termination, Connected Sheets, and AMD Epyc instances.
> Kubernetes pods can be uncleanly terminated at any time for any reason
Not true, pods can be gracefully shutdown, see https://cloudblog.withgoogle.com/products/gcp/kubernetes-best-practices-terminating-with-grace/amp/
> The clustering protocol also seems to assume that all members have stable identities and IP addresses, but that's obviously not the case in Kubernetes, where each new pod has a new identity and new IP address.
Both not true: Orleans cluster managed by a dynamic membership table which could be implemented by various tools(azure table, zookeeper, Kubernetes crds(etcd internally), etc), so nodes don't need static ip addresses
also, in Kubernetes, you can deploy application as statefulset, by this way, pods will have stable identities
> Orleans was introduced by one person who has a background in distributed computing. Unfortunately, he's the only one in the organization with such a background. After he left, nobody could debug clustering problems.
Need source and proof for this one
Please don't post ridiculous opinions about things you are not familiar with, both Kubernetes and Orleans.
I have built successful products by Orleans & Kubernetes since two years ago, and now Orleans get better integration for Kubernetes than that time
edit: formatting & typo
Re: worker processes
Have a look at GCP EventArc. It's a new way to trigger cloud run instances. You could create an EventArc trigger that wakes up a worker image, or some such. Basically,EventArc enables serverless event driven design across all GCP.
https://cloudblog.withgoogle.com/topics/developers-practitioners/eventarc-unified-eventing-experience-google-cloud/amp/
GCP and Azure are offering AMD Epyc Rome based instances as well. Intel is losing their death grip on the data center space quickly.
https://cloudblog.withgoogle.com/products/compute/amd-epyc-processors-come-to-google-and-to-google-cloud/amp/
https://azure.microsoft.com/en-us/blog/announcing-new-amd-epyc-based-azure-virtual-machines/
> The recent HN threads about excel made me think there's definitely room for a new kind of excel that works well for big data.
Check out Google Connected Sheets: https://cloudblog.withgoogle.com/products/g-suite/connected-sheets-is-generally-available/
Google AI team did a very good presentation and blog post about this and other common problems
https://cloudblog.withgoogle.com/products/ai-machine-learning/best-practices-that-can-improve-the-life-of-any-developer-using-jupyter-notebooks/amp/
Nearly a year behind Google
https://cloudblog.withgoogle.com/products/compute/google-cloud-first-to-offer-nvidia-tesla-t4-gpus/amp/