---
title: "Ray | Skills We Assign For | Azendo"
description: "Ray for distributed Python — scaling existing code, tuning and serving, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/ray/"
---

[Skills](https://azendo.co/skills/) MLOps and model delivery 

# Ray.

Ray is a framework for distributed Python, scaling from a laptop to a cluster with libraries for hyperparameter tuning, distributed training, reinforcement learning and model serving.

## Where Ray fits on a long engagement.

Ray's appeal is that it distributes ordinary Python rather than requiring a rewrite into a specific paradigm. Functions and classes become remote tasks and actors with decorators, so existing code scales with comparatively little restructuring.

Ray Tune is the component most teams get value from first. Distributing hyperparameter search across a cluster, with early stopping for poor trials, turns a search that would take days into one that takes hours — and that changes how thoroughly a model is explored.

## What an assigned team does with Ray.

Distributed systems fail in ways single-machine code does not. Worker failures, memory pressure on individual nodes and network issues all need handling, and a job that ran locally can fail non-deterministically at scale.

Operating a cluster reliably is platform work alongside the modelling, scoped under [devops managed services](https://azendo.co/services/cloud-and-devops/).

## What we use Ray for.

* Scaling existing Python Distribution without rewriting into a different paradigm.
* Hyperparameter search across a cluster Days of search compressed into hours, with early stopping for poor trials.
* Failures handled at scale Worker loss and memory pressure designed for rather than encountered.

## How Ray capacity is assigned.

Distributed compute work is assigned across AI and platform capacity, since the cluster is operated as production infrastructure.

## Roles we assign Ray for

* [ML Platform Engineer MLOps engineering](https://azendo.co/services/mlops-engineering/ml-platform-engineer/)

## Service lines it sits in

* [MLOps engineering](https://azendo.co/services/mlops-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in mlops and model delivery

* [TensorRT — skill we assign for](https://azendo.co/skills/tensorrt/)
* [Model registry — skill we assign for](https://azendo.co/skills/model-registry/)
* [Weights & Biases — skill we assign for](https://azendo.co/skills/weights-and-biases/)
* [Comet — skill we assign for](https://azendo.co/skills/comet/)
* [Neptune.ai — skill we assign for](https://azendo.co/skills/neptune-ai/)
* [DVC — skill we assign for](https://azendo.co/skills/dvc/)
* [Feast — skill we assign for](https://azendo.co/skills/feast/)
* [feature stores — skill we assign for](https://azendo.co/skills/feature-stores/)

## Tell us what your roadmap needs Ray for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)