Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

How QRebel fits into DevOps

[The following is a blog by Ido Benmoshe, V.P. of global support & professional services at Rogue Wave Software]

Applications drive the success of a business and the competitive market mandates performance and efficiency of both the software development lifecycle and the applications themselves. Application performance and reliability are key differentiators to end users but they also impact direct costs as more payload is moving to utility-based consumption. Better performance and efficiency translate to lower infrastructure cost and higher end-user satisfaction.

Calculating the ROI on DevOps

The development process must address the application quality needs but also consider the time to market and flexibility – essential in keeping up with the evolving digital consumer markets. Expansion of mobile, IoT, and web demand flexibility and speed, driving companies to adopt CI/CD to accelerate development cycles while maintaining high quality. In the “Economics behind continuous delivery” paper, we have introduced a model for calculating the tangible gains resulting from adopting CI/CD or DevOps practices:

  • • Revenue gains from accelerated time to market of new functionality
  • • Gains from enhanced IT team productivity and reduced waste
  • • Gains from cost reduction of application failures resulting from increased quality
  • • Gains from flexibility in IT environments

The model is designed to present an economical buyer, or application’s business owner, with the hard ROI supporting what developers and operations teams have experienced in practice. One of the key requirements of a successful DevOps process that can maximize gains is the ability to provide sufficient application diagnostics and problem resolution capabilities.

In a modern DevOps environment, build pipelines are launched frequently or on every code check in. The large number of dependencies, microservices comprising an app, and reliance on open source code results in complex transactions that are difficult to break down and analyze. Ensuring high code quality, identifying regressions, and optimizing performance will reduce the need to halt the release cycles. Tools accelerating problem detection and immediate root-cause resolution become a necessity of the CI/CD process to provide developers with a quick way to perform their analysis and address regressions.

Choosing the right tools

Combining static and dynamic analysis tools is a good practice to increase defect coverage and provide developers with the insight and drill-down data to prevent defects from slipping through, ultimately delaying the builds. XRebel and JRebel have become the Java developer’s standard for optimizing application performance and developer productivity.

The new member of the product family, QRebel, takes this proven technology a step further in the release cycle. Providing dynamic problem and regression detection using low-level JVM monitoring technology in the automated testing cycle, QRebel provides DevOps engineers with the data they need to pass or fail builds while developers get the insight they need to resolve problems remotely without accessing or interrupting the testing environment. QRebel detects slow requests and degradation between builds, exceptions, and excessive I/O pinpointing the root cause of the problem, including the specific microservice, transaction, or method that caused the error.

With QRebel, performance issues are eliminated early, maximizing the benefit to the business by allowing the CI/CD process to continue smoothly and prevent performance issues and defects from hitting end users.

To learn more about QRebel and try it out for yourself, visit qrebel.com.