Storage-optimized Z4D machine family, now GA, is designed for IO-intensive workloads
From the source: Google Cloud BlogToday, we’re excited to announce the general availability of our next-generation Storage-optimized Z4D machine series in Google Compute Engine with both Virtual Machine (VM) and bare-metal instances. We built Z4D for IO-intensive and business-critical workloads that require large local storage capacity and high storage performance, including SQL, NoSQL, KVrocks and vector databases, data…
Read the full story on Google Cloud BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Containers & Kubernetes
OpenShift vs managed Kubernetes (EKS/AKS/GKE) for regulated workloads
For teams in financial services, government or healthcare: which did you choose and what tipped it: compliance evidence, support, cost or skills?
How many Kubernetes clusters do you run, and how do you keep upgrades sane?
Fleet size, managed vs self-managed, and the tooling that keeps version upgrades from becoming a quarterly fire drill.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from Google Cloud
Recent updates from Google Cloud, so you can tell whether this is a one-off or part of a pattern.
More in Containers & Kubernetes
What other companies in Containers & Kubernetes are doing. The category page shows who’s active, side by side.


