Tooling

Kubernetes is great because of its almost limitless configurability. But this configurability makes it hard to ensure that best practices are followed consistently across your cluster.

When starting a new job, have you ever asked yourself: How much time should I spend learning about the code? The product? The process? Was I expected to know Technology/Framework/Design Pattern X?Is my ticket taking too long?

Let’s get DevOps to mean Service Ownership again. We broke DevOps. And it’s preventing us from building. When the first cloud providers emerged in the mid-2000s, they unlocked a new superpower: the ability to near-instantly provision hardware. Service-oriented architecture and microservices developed as a new architectural pattern. As a result, DevOps emerged as a practice to organize engineering teams around those new services - combining development and operations responsibilities onto the same team.

OpsLevel is intended to be your source of truth for microservice and ownership information. Today, we’re very excited to announce that we’ve taken a leap forward towards that vision with the launch of our GraphQL API.

At OpsLevel, we’re big fans of the 2015 MacBook Pro. The newer 2019 MacBook Pro has some great features like Touch ID, 32 GB RAM, and USB-C power delivery that you can plug on either side. Unfortunately, it also suffers from a failure prone butterfly keyboard design and the dreaded Touchbar. The 2015 MacBook Pro was the last model manufactured by Apple before the switch to Touchbar and and the butterfly keyboard.

OpsLevel is a fantastic source of truth for all of the information around the microservices in your architecture, including all the tools you use to operate each of your microservices. But it’s not always the easiest to find and discover this information when you really need it - say during a major incident, or during a gameday.