Our own Dave Rosenberg recently hit the press circuit, and returned with two Q&A sessions that help to explain what Nodeable does, and why it matters.
The first involves Dave’s prediction that in 2012 IT, and particularly DevOps, will seek to measure everything.
Along with the rise of cloud-to-cloud application networks, I also expect to see a great deal of interest in the monitoring and management of cloud transactions. In fact, this may be where we start to see the rubber hit the road in the DevOps world as different user groups within an organization have vested, but different interests in ensuring that data arrives quickly and consistently.
To that end, we’ll see a growth in the analysis of communication in the cloud and solutions that address everything from the “digital exhaust” associated with every layer of the stack-from each transaction to the system management aspects of virtual machines themselves.
Given Dave’s prediction, it’s perhaps not surprising to see that Nodeable is trying to solve this problem of complex system data with a clean, unified interface, as Dave notes in a separate interview:
The short version is that we struggled to make the existing tools match the new world of cloud services, which are quite fleeting. It didn’t make sense to script and automate resources that were transient, and none of the tools were designed in a multi-tenant fashion, meaning we didn’t have a breadth of deployment options.
And, the majority of the available tools are ugly and hard to use. We wanted to simplify the management tools and take advantage of the modern compute power the cloud offers….
From the Nodeable perspective, we think we can define and provide a layer in the new cloud stack – one that takes advantage of the “digital exhaust” we get from systems and adds intelligence to data. The gathering and analysis of this data leads into a systematic approach to managing these services based both on deterministic responses and predictive analytics.
Which means that Nodeable isn’t necessarily replacing other system management solutions, but rather complements them by ingesting “exhaust” from these and other systems (be it Salesforce, AWS, or Jira), thereby giving DevOps a single pane of glass through which to see relevant system events and act upon them.
Just don’t make the Nodebelly angry.