Systems | Development | Analytics | API | Testing

Current 2025 featured two days of engineers figuring out how streaming tech needs to evolve in an AI-driven world. Gone are the days when talks focused on basic Kafka setup. This year, everyone was tackling complex integrations, developer happiness, and practical AI implementation. Still, the event drew a range of people, with plenty of new faces stopping by the Lenses.io booth – clear evidence that Kafka and data streaming continue to attract newcomers.

Lenses 6.0 (code-named Panoptes after the Greek mythical character with many eyes) is generally available. It brings a multi-Kafka developer experience and complete autonomy to streaming data.

You didn’t become a developer to spend hours hunting down missing messages, or debugging consumer issues. Yet here we are. Valuable dev time evaporates as you wrestle with Apache Kafka, or wait for a central team to unblock you, when you should be finding, prepping, and shipping streaming data in minutes. Lenses Community Edition tackles these everyday frustrations.

New York City, US - February 12, 2025 - Lenses.io, a data streaming innovation leader whose software helps developers power the world’s largest businesses, today announces the development of an enterprise grade and vendor-agnostic Kafka-to-Kafka replicator. It will enable organizations to share streaming data across different domains, in order to keep up with real-time data demands as AI adoption grows.

As organizations adopt specialized streaming technologies, real-time data is increasingly distributed across multiple domains, clouds, and locations. With the rapid evolution of streaming-dependent technologies, companies need the ability to pivot between providers almost instantly to spread risk and maintain performance (just look at the January DeepSeek-R1 LLM news).

Buckle up, we’re past the AI hype. Now, it’s about making intelligent systems that act on our behalf. In 2025, AI isn’t just a tool– it’s becoming our core way of operating, powered by real-time data. How we stream, manage and monetize that data will define the next generation of business. Here, we zoom into four examples of what autonomous real-time intelligence could look like in the coming year.

The need to democratize and share data inside and outside your organization, as a real-time data stream, has never been more in demand. Treating real-time data as a product, and adopting Data Mesh practices, is the way forward. Here, we explain the concept through a real-life example of an airline building applications that process data across different domains.

Democratizing and sharing data inside and outside your organization, as a real-time data stream, has never been more in demand. Treating data as-a-product and adopting Data Mesh practices is leading the way. Here, we explain the concept through a real-life example of an airline building applications that process data across different domains.

Organizations today face complex data challenges as they scale, with more distributed data architectures and a growing number of teams building streaming applications. They will need to implement Data Mesh principles for sharing data across business domains, ensure data sovereignty across different jurisdictions and clouds, and maintain real-time operations.

Every enterprise is modernizing their business systems and applications to respond to real-time data. Within the next few years, we predict that most of an enterprise's data products will be built using a streaming fabric – a rich tapestry of real-time data, abstracted from the infrastructure it runs on. This streaming fabric spans not just one Apache Kafka cluster, but dozens, hundreds, maybe even thousands of them.