Resources

The ongoing pandemic is forcing companies to modernize their operations and invest in new digital technologies. But as companies double down on digital transformation and race into the cloud, they are creating a considerable amount of technical debt in the process.

Burnout can affect us all, and unless we watch for the causes and signs in our teams and organizations, we may not see it coming until it’s too late.

These days we all feel the pressure of shipping more frequently and keeping up with the demands of our customers.

We’re announcing a $15M Series A funding and OpsLevel’s vision for accelerating software teams with developer portals.

Software developers have been putting badges on their repositories for a long time. Since they’re easily recognizable and have high information density, badges make it simple for developers to signal (or understand) things like code quality, test status and coverage, version, framework, or adherence to various standards.

In many companies, as the size of the organization grows, the complexity of the available infrastructure, services and APIs grows at an even faster rate.

With services, proper reliability is critical to success. But many don’t fully understand what reliability entails. In this post, we’ll set you up for success with an essential guide to understanding and improving service reliability.

Microservices will change. This is inevitable. But how do you manage that change to ensure your consumers don’t feel unnecessary disruption? Alternatively, what best practices can you follow to make migrations easy?

All over the globe, teams are scrambling right now to triage the impact of the recently announced Log4j vulnerability on their services and applications. Rather than reinvent the wheel, here’s a snippet from an informative Cloudflare blog post that puts CVE-2021-44228 in context:

A security vulnerability was published on December 12th, 2021 by the NIST for Log4J version 2.14.1 or earlier, dubbed CVE-2021-4422. OpsLevel does not use Java in its technology stack and is not affected by this security advisory.

Applications, products, and systems have become more and more complex. Microservices, dependencies, and external services provide greater functionality and improved reliability.

Shifting to a microservice architecture comes with well-known benefits. Isolation between systems and teams means feature teams can iterate faster and the entire software engineering organization can scale with more efficiency and agility.

Event-driven architecture (EDA) is more scalable, responsive, and flexible than its synchronous counterpart. That’s because it processes and distributes information as it arrives instead of storing it for processing when a client requests it.

Improving your microservice security isn’t like improving the security of a monolith application. Microservices provide lots of flexibility for application developers.

Welcome to Level-Up, an exclusive interview series with standout engineering leaders who share what’s top of mind for them. This interview puts the spotlight on Diederik Van Liere, VP of Data & Engineering at Wealthsimple. Let us know who we should talk to next!

Testing microservices can be difficult. Often, we underestimate these difficulties when first working with microservices.

Engineering organizations often look for ways to improve their engineering teams’ efficiency. The more efficient the team, the faster they can ship new features and products to their customer base. From this need for efficiency, combined with developer empathy, we’ve seen the rise of DevOps and site reliability engineering across the industry.

When you’re designing a microservice architecture, there are a lot of questions you have to answer. Some of them make themselves apparent very early in the process.