Spring Cleaning at OverOps: How (and Why) We Changed Our DB Cleaning Strategy

There comes a time in the life of any application that small things we let slide become unignorable issues. For us, it happened when, after years of writing and executing code, our DB’s free disk space started to run out. Each passing day brought us closer to our eventual doom, and we finally had to allocate the time to fix the problem.


The Cake is NOT a Lie: 5 Java Frameworks to Support Your Microservices Architecture

“The microservices trend is becoming impossible to ignore,” I wrote in 2016. It’s still true, although it’s certainly grown to more than just a passing fad. Back then, many would have argued this was just another unbearable buzzword, but today many organizations are reaping the very real benefits of breaking down old monolithic applications, as well as seeing the very real challenges microservices can introduce.

Maintaining Code Quality During the Container Revolution with OverOps

Microservices are taking over the software world, affecting how software is designed, written and delivered. Current tooling, such as log aggregators and APM solutions, struggle to provide the depth of context needed to maintain and troubleshoot these new containerized applications. Meanwhile, large enterprises don’t have enough data to correlate issues across containers, deduplicate them and find the root cause of the problem.

Strangler Pattern: How to Deal With Legacy Code During the Container Revolution

When we say “technical debt”, what’s the first thing that comes to your mind? Is it the accumulation of code in an outdated system that’s seen changes from tens, or even hundreds, of developers over the years? Is it a codebase with poorly-written methods following convoluted logic and hard-to-follow patches for production issues? It’s both, really.