The solution is stable.

I would rate the stability of the solution an eight out of ten.

We had high uptime for it. We didn't have too many issues with the releases and the versioning that they have beeen putting out. Mostly, everything went smoothly even with major foundational changes. Overall, anytime you're doing a foundational change, there will be some growing pains, and you expect that with any tool set.

We have had no stability issues.

It all seems to be very solid and stable.

I rate Chef a nine out of ten for stability.

We do put a lot of stress on it from the QA, staging, and servers. We have a CI/CD pipeline continuously running as the developer commits the code to Chef and Puppet, which are always up and running.

I'm satisfied with the stability of Chef. I'm satisfied with its performance, but it's the same with some of its competitors, e.g. there are alternatives. Ansible from Red Hat is also a good tool. We are also using it. The tool we use depends on the use case and the customer, e.g. we can use different tools.

We put quite a lot of stress on it, especially in our larger environments.

The tool was fairly stable.

It's quite stable, we hardly see surprises. Its deployment is very smooth.

The product is quite stable. We hardly experience any surprises. Its deployment is very smooth.

I have had minor issues with development and configuration but we have an in-house team that takes care of most of it.

We have some issues in Brazilian region with stability. However, in US region, we have no issues with stability.

The stability is good.

It is stable most of the time. There hasn't been any downtime.

We did not go with the traditional architecture, so we decided to use the AWS systems by decoupling the traditional architecture.

It's working great. It's stable. We try to produce real-world scenarios with the students as much as possible.