I am a fan of Gearman to schedule and dispatch distributed jobs, Redis as a collaborative blackboard, and GlusterFS to share models across multiple systems and make bulk data available across the entire system (usually referenced in the blackboard as a pathname). Source: about 1 year ago

If you're not relying on support, then I would probably standardize on the latest packages available from gluster.org. Source: about 3 years ago

Infrastructure as code (IaC) allows DevOps teams to define the end state of the required infrastructure and deploy it using a template-based approach. Public cloud platforms each provide proprietary IaC tools, such as Azure (ARM Templates and Bicep), AWS (CloudFormation), and GCP (Deployment Manager). - Source: dev.to / about 1 year ago

Start with the google docs https://cloud.google.com/deployment-manager/docs. Source: over 1 year ago

Cloud Deployment Manager: Templated infrastructure deployment 🔗Link 🔗Link. - Source: dev.to / almost 2 years ago

When exploring options on how to deploy the architecture we briefly considered Google Cloud Deployment Manager. Upon further investigation we were led to use Terraform instead. It was evident that Cloud Deployment Manager did not have the necessary support for the resource types that we were trying to create. Many of the supported resource types were still listed in beta. - Source: dev.to / almost 2 years ago

Deployment Manager templates give declarative language choices rather than imperative ones; this means that DevOps teams may tell Deployment Manager what a final deployment should look like, and GCP will automatically utilize the tools and procedures. When an excellent deployment method is created, it is saved so that it may be repeated and scaled on demand. Source: about 2 years ago