Systems | Development | Analytics | API | Testing

Recently, we created the Sauce Labs Open Program Office to focus our attention internally on how we support and contribute to the open source community. Last week, we proudly launched a new web site with comprehensive information about the office, including best practices, contribution guidelines for the Sauce team, and a new blog where Diego Molina and Christian Bromann will write regularly about all things open source. This article is cross-posted from the new blog.

Back in 1977, an English mod/rock band called The Jam released a track called “The Modern World.” The same year also saw the dawn of the home computer, with the Apple II and Commodore PET 2001 going on sale at a time when the mainframe was going strong. Fast forward to 2020, and, despite many false claims of its death, the mainframe remains strong; however, to get the most value of from the data inside, mainframe modernization is key.

Even though only 11 years old, Node.js has emerged to be one of the most popular web development frameworks in the last decade. I’m a big Javascript fanboy, and thanks to Node.js, I can write Javascript code outside the browser to create server-side web applications that are non-blocking, lightweight, fast, robust and scalable.

Working with Apache Kafka and real-time applications comes with challenges. Visibility into the deployed applications and their dependency on what we call the “data fabric” is one of them (For the sake of this blog, it means Kafka and all its state and configuration). If you’ve built a multi-tenant real-time data platform with Kafka, where teams are deploying applications outside your jurisdiction, this is where the pain is particularly acute. It goes something like this.