Platform engineer

Embracing a microservice architecture typically also means deploying much more frequently, which can seem scary. But favoring many incremental deploys is actually a sound risk mitigation strategy since changes tend to be smaller and more isolated.

A service catalog is a valuable asset for any growing engineering organization delivering software at scale. But valuable assets aren’t created or earned easily. That’s why, at OpsLevel, we’re always thinking about ways to make building and maintaining an up-to-date service catalog simpler. Recently we upgraded our Discovered Services capabilities to do just that.

Over the last decade, shrinking feedback loops have been a core part of building and delivering software. Across every phase of development and delivery, software engineering organizations are getting faster answers to questions like:

Let's explore Backstage, the problems it attempts to solve, and considerations to make before bringing it into your organization.

Over the last week, the team at OpsLevel completed its largest HackDay ever. OpsLevelers demoed 15 different projects, spanning everything from our infrastructure and CI/CD pipelines to our Applicant Tracking System and assets for acquiring and onboarding customers. Even our CEO carved out time to write some code–though he admitted his UI was lacking.

Today, Kubernetes is the de facto standard for container orchestration, running in approximately half of all containerized environments. Platform and infrastructure teams of all shapes and sizes are accustomed to operating Kubernetes in order to run their organizations’ microservices (and applications) at any scale.

More software, more problems? Software is eating the world and that means more people and teams are developing software. To stay current and competitive, modern organizations are scaling their software engineering teams.

Our software ecosystems grow more complex every year. With new frameworks, dependencies, and technologies to help automate or simplify every step of the development life cycle, keeping track of requirements that provide reliability and security can become difficult. And that’s why production readiness reviews and checklists help eliminate cognitive load. They let you focus more on features or potential failure points.

Years ago, end-to-end software development involved dividing tasks based on where they fell in the system life cycle. One team wrote the code. Then another team deployed it to production. And yet another team monitored and maintained the service. This led to a lot of friction, needless handoffs, and bottlenecks.