The Maverik Debugging Challenge
The Maverik customer loyalty card website was developed several years ago as a Java monolith. In 2018, Maverik began replacing the legacy Java monolith architecture with modern Java-based microservices running on a Kubernetes stack.
Before Rookout was introduced, during development and staging and while the new microservices architecture was not yet in production, Maverik developers used the traditional debugging approach: Using an APM (Application Performance Management) solution, they would identify where a problem might lie. Then, they would add log lines and re-release the code to capture debugging data required to pinpoint the issue’s root cause.
Adding logs entails a 5-hour rebuild/test/redeploy process, which significantly slows the debugging speed even in the current pre-production environment. This becomes an even bigger challenge when the new microservices solution is released to production — a more controlled environment where code-changes take even longer to approve and release.
Getting Started with Rookout
One early adopter at Maverik, however, chose to dig into Rookout even before the new system was released and was gratified to discover how quickly it allowed him to debug issues. Jerrie Pineda, Maverik’s Enterprise Software Architect, found that Rookout can ease Maverik’s refactoring effort by enabling him to resolve issues faster than ever before.