
As a Software Engineer who collaborates with both the Development and the SRE teams, I find Turbonomic to be a valuable tool as it grants visibility and strategic insight to our hybrid cloud infrastructure, which is composed of both AWS and on-prem VMware. Our architecture is complex, as we focus on building internal enterprise applications such as our Human Resource Management System (HRMS), as well as our fully automated billing system. The architecture also utilizes microservices along with Node.JS and Python.
Before Turbonomic, it was mostly guesswork when managing resources for the environments we provisioned. We had to provision more CPU and Memory than required to work around latency issues during peak times. Turbonomic’s solution offers a considerable amount of information pertaining to the resources and how they impact the applications. The solution has also aided managing a lot of things related to Kubernetes pods. It doesn’t show us a single hot node and call it a day. It shows us the various automations it can carry out to ‘remove’ some resource burden by allocating pods and nodes dynamically.
It also addresses the gaps between engineering and operations. If we have to deploy a resource-intensive billing system, the operations team can examine the dependency mapping to understand how the new system impacts the overall infrastructure and what trade-offs can be made in the systems to accommodate the new billing system. Review collected by and hosted on G2.com.
We can expect this to take considerable time to set up as a connector to all your tools, spanning APM, cloud service providers, Kubernetes, vCenter, etc.
In addition, gathering the many alerts and recommendations produced by the system will take considerable time. The system will become very pushy and nagging if the recommendations are not acted on. For example, one of the recommendations was to downscale a certain number of workers to optimize the cloud resources. One of the workers was used to process background tasks. The recommendation was based on the worker being underutilized on average, but it was actually downscaled the worker that processed the tasks. If time is not spent continually to manage the system, then the system will have to be configured to operate without any automation.
The user interface is probably the biggest hurdle for the non-technical members of the team, and probably the most overwhelming facet of the system, namely that it is not user friendly and gives little indication of your overall system performance versus your cloud costs. Review collected by and hosted on G2.com.