Welcome!

VictorOps Helps Your IT/DevOps Team Solve Problems Faster

VictorOps Blog

Subscribe to VictorOps Blog: eMailAlertsEmail Alerts
Get VictorOps Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by VictorOps Blog

Microservices, Containers, Code Ownership, and Continuous Support By Todd Vernon Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Small Image: Courtesy Akana, Inc Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years. Spoiler Alert: Microservices are where it’s all going, Container systems like Docker or Kubernetes are a huge enabler of that vision, code ownership flourishes in this environment, and DevOps promotes this culture and ecosystem of tools that unlock the huge social gains of all of it. Let’s unpack that long sentence a... (more)

Loops On Loops: How Feedback Enables Improvement By @JasonHand | @DevOpsSummit #DevOps

Loops On Loops: How Feedback Enables Improvement By Jason Hand We all remember the game from our childhood where one person whispers a phrase to the person directly next to them, who in turn shares the phrase with the following person in line. This continues through a group of people until it makes its way back to the original source. The game went by many names: Telephone, Grapevine, and Operator, among others. The point of this exercise was primarily to demonstrate how easily information can become corrupted by a lengthy path through which it passes. Minor and major alteration... (more)

SBT, Scrooge, Intellij and You By @VictorOps | @DevOpsSummit [#DevOps]

How to Set Up a Playdate Between Scala, Thrift, Scrooge, SBT and Intellij By Nick Isaacs Here at VictorOps, we are going through the process of overhauling the serialization framework that we use for inter and intra process communication. We evaluated several great options including Kryo (and its Scala companion Chill), Protobuffers, and Thrift. In the process, we put together a little test project to help us decide which of these choices was right for us. Testing Thrift posed some challenges as the tooling, while quite mature, wasn’t quite as plug-n-play with our local developme... (more)

NOC, NOC… Who’s There? By @VictorOps | @DevOpsSummit [#DevOps]

By Bryce Ambraziunas In part one of this series, our COO tackles the history and purpose of the NOC. A NOC, for those who don’t know, stands for Network Operations Center and, quite simply, is how large organizations with complex systems monitor them. Early versions of the NOC came about in the early 1960’s when there was a need for humans to actively take part in noticing, and fixing, complex errors. An early NOC was opened by AT&T in New York to display switch and route information, in real-time. It’s easy to see why a NOC used to be considered essential for larger companies ... (more)

Hidden Lessons of Incident Management By @JasonHand | @DevOpsSummit #DevOps

Hidden Lessons of Incident Management By Jason Hand One of the most common early goals of implementing DevOps principles is a deep understanding of our systems in a stable state. However, this objective is not a “once and done” effort. It is important to continuously circle back in some form (a feedback loop) as changes are introduced. It’s an ongoing exercise for an entire organization as our processes, tools, and teams improve continuously over time. In many cases during these beginning stages of DevOps transformations, agreeing on a starting point is where much of our time is ... (more)