G2

Alexander Y.

Senior PHP Developer

Small-Business (50 or fewer emp.)

9/6/2024

"A Game-Changer for Kubernetes Development Workflows"

4/5

What do you like best about Garden.io?

The declarative configuration approach using YAML files makes it easy to define and manage our entire application stack. I particularly appreciate how Garden builds a graph of our stack, making it much easier to understand and manage dependencies between services. Review collected by and hosted on G2.com.

What do you dislike about Garden.io?

While Garden.io is powerful, it does have a learning curve, especially for team members who are new to Kubernetes or microservices architectures. The initial setup and configuration can be time-consuming, and sometimes the error messages aren't as clear as I'd like them to be. Review collected by and hosted on G2.com.

What problems is Garden.io solving and how is that benefiting you?

Garden.io is solving several critical challenges in our Kubernetes-based microservices development workflow:

Environment Consistency: Garden.io ensures that our development environments closely mirror our production setup. This has drastically reduced the "it works on my machine" problem, saving countless hours of debugging environment-specific issues.

Faster Iteration Cycles: The in-cluster development feature allows us to develop and test changes directly in a Kubernetes environment. This has significantly sped up our development cycles, as we can immediately see how our changes behave in a realistic setting.

Dependency Management: Garden's stack graph functionality has given us a clear view of the dependencies between our services. This visibility has improved our architecture decisions and made it easier to manage complex interactions between microservices. Review collected by and hosted on G2.com.