Systems | Development | Analytics | API | Testing

Jonas Best & Patrick Polster Kafka migrations are one of the riskiest infrastructure projects a platform team can take on. Miss a dependency and a downstream app starts reprocessing events it already handled leading to breaking SLAs and eroding trust with application teams. Migrate without visibility and you risk a major production issue. The instinct is to reach for a replication tool and call it done. But replication is only one piece of the puzzle.

At Lenses, our goal has always been to help organizations get the most out of their streaming data. We started with visibility into the Apache Kafka, moving up to the part that drives value, the application layer and now the Agentic layer. Lenses 6 moved us into a multi-Kafka world, as increasing, our clients aren’t just running on one type of Kafka anymore, and as sovereign cloud becomes increasingly topical (no pun intended) this is only increasing.

Enterprises in 2026 are under increasing pressure to modernize applications, adopt hybrid cloud architectures, and streamline operations—but their expanding and aging VMware footprints have become a major obstacle. As VMware licensing models evolve and operational costs climb, reducing or restructuring this footprint has become just as critical as adopting new platforms.

There’s something powerful about stepping away from your day-to-day work and being surrounded by people asking the same questions you’ve been thinking about: At JSConf Spain, those answers don’t come from a single talk. They emerge from patterns — ideas that repeat across different speakers, different companies, and different perspectives.

An AI Data Gateway is a secure intermediary that connects enterprise data sources (like databases and file systems) with AI systems. It simplifies how AI accesses data while enforcing strict security, compliance, and governance measures. Instead of allowing direct access to sensitive data, the gateway uses secure REST APIs to control and monitor all interactions.

Contents AI is now embedded across the entire software development lifecycle. Developers use it to generate code. Product managers use it to prototype features. Teams use it to move from idea to deployment faster than ever. Code moves faster. Features ship more frequently. Iteration cycles shrink. Across industries, companies that embrace this speed have a distinct competitive advantage. But in highly regulated industries, including financial services, speed can’t come at the cost of quality.

The contemporary mobile ecosystem is incredibly complicated. Applications today are not standalone anymore; they are dynamic, heavy in features, and constantly communicating with cloud solutions, wearables, and IoT devices. Although the use of traditional test automation has contributed to enabling engineering teams to remain in step with agile delivery, the sheer number of fragmented devices and continually changing user interfaces has revealed the limitations associated with it.