Atlassian recently published how it exceeded 99.9999% of availability with its Tenant Context Service. Atlassian achieved this high availability by implementing highly-autonomous client sidecars, able to proactively shield themselves from complete AWS region failures. Sidecars query multiple services concurrently to accomplish this goal and ensure that requests are entirely isolated internally. (Read more on InfoQ)

Slack recently published how it implemented the Circuit Breaker pattern to improve its CI/CD pipeline availability. Before this project, engineers at Slack saw challenges as peak request volumes in internal tooling caused cascade failures in dependent systems. Since completion, engineers saw increased service availability and fewer bad developer experiences like flakiness from failing services. (Read more on InfoQ)

Spotify engineers recently published how they standardized architecture diagrams at the company. They defined a standard system model named the Spotify Software Model and adapted the C4 model to visualize it. This combination created a shared language used across the organization, which helps communication, aids decision-making, and supports Spotify’s software’s evolution. (Read more on InfoQ)

Uber recently introduced Unified Signup and Login (USL), an effort to consolidate signup and login experiences across all Uber apps and services. USL lowers the engineering complexity and maintenance overhead and allows faster rollout of security policies and fixes. Over the last two years, Uber rolled out USL and currently, more than 78% of Uber’s traffic has adopted USL. (Read more on InfoQ)

Lightbend recently launched Kalix, a new PaaS offering for building cloud-native, business-critical applications using any programming language with no databases. Kalix is a unified application layer that pulls together the necessary pieces for writing software and abstracts their implementation details. Lighbend intends for it to provide developers with an innovative NoOps developer experience. (Read more on InfoQ)

Netflix engineers recently published how they built Studio Search, using Apache Kafka streams, an Apache Flink-based Data Mesh process, and Elasticsearch to manage the index. They designed the platform to take a portion of Netflix’s federated GraphQL graph and make it searchable. Today, Studio Search powers a significant portion of the user experience for many applications within the organisation. (Read more on InfoQ)

Dropbox recently published how it made the camera upload process for Android faster and more reliable. Dropbox engineers removed shared Android and iOS C++ code and replaced it with a platform-native Kotlin implementation. The engineers are pleased with the decision to rewrite the process, stating that error rates went down and upload performance greatly improved. (Read more on InfoQ)

LinkedIn recently published how it handles overload detection and remediation in its microservices. Its solution, Hodor, provides an adaptive solution that works out of the box with no configuration. It is a platform-agnostic mechanism to run overload detectors and load shedders inside the monitored process that samples load and sheds traffic from within the application’s processing chain. (Read more on InfoQ)

Andrew Harmel-Law recently published an article describing a decentralised, scalable software architecture process based on the “Advice Process”. The Advice Process promotes software architecture by encouraging a series of conversations driven by an empowering, almost anarchistic, decision-making technique. It comprises one rule – anyone can make an architectural decision. (Read more on InfoQ)

The Cloud Native Computing Foundation (CNCF) recently announced that it accepted the Distributed Application Runtime (Dapr) as a CNCF incubating project. This statement follows an earlier announcement by Dapr, announcing the formatAirbnb recently detailed how it designed and built a unified architecture for collaborative hosting. This architecture streamlines the development process of new products, as engineers only need to know about one central framework that will cover all hosting use cases. This framework encapsulates the specific types of collaborative hosting, freeing the engineers from the need to worry about them. (Read more on InfoQ)