DevOps

Microservice architecture has become a staple in modern software development, known for its approach of breaking down applications into small, independent services that communicate with each other. While it offers considerable benefits such as scalability, flexibility, and faster deployment times, it also introduces a range of challenges. This article explores these challenges in depth, providing a richer perspective supported by data and examples that will help software architects, developers, and business stakeholders understand and navigate the complexities of this architecture.

Need to add cost data to your services? Maybe you want to track which services process PII? Custom Properties, helps you track any data *consistently* across all your services.

Embark on a journey towards production readiness excellence with automated processes and insights from dev portals.

An intro to how platform engineers benefit from incorporating an IDP.

The hidden costs of DIY'ing your dev portal.

Here’s a recap of updates and fixes released this month.

Nothing scary here! Read up on latest features and updates from the month of October.

In the first part of this series, we mentioned that great Developer Experience (DevEx) means optimizing work and removing friction so your developers can easily get in and maintain flow state. In this section, we will explore how tooling can impact flow state and what we can do to improve our tooling choices, whether it be open source, off-the-shelf commercial software, or designing your own in-house tools.

Great developer experience (DevEx) is what you get when developers can easily achieve and maintain flow state at work. This article begins a series where we tackle all of the areas that affect flow state and impair your developer experience at your company and provide example metrics and suggestion to help you operate like a potential future unicorn.