Systems | Development | Analytics | API | Testing

To better guide our roadmap, Fivetran uses revenue-weighted feature usage (RWFU) — a metric that shifts the focus from raw adoption to real business impact.

October marks Cybersecurity Awareness Month. It’s a timely reminder that the files you touch, share, and rely on every day often hold your most valuable data and are exactly what attackers are after. Unstructured data, like spreadsheets, documents, logs, and backups, makes up the majority of your business data. That’s what makes it the prime target for ransomware.

Imagine an airline system monitoring traffic around an airport. If it detects a major delay, countless systems may need to react instantly: Ground operations to adjust flows. Some of these systems will still connect via API, traditional MQ or iPaaS technologies, but the data’s volume and urgency and the ease of decoupling apps make architecting with Kafka the better fit. The natural question is: should all these applications & systems connect to the same Kafka cluster?

In the evolving landscape of agentic systems, Confluent and Google Cloud together emerge as critical enablers, providing the real-time infrastructure that underpins efficient, reliable, and intelligent data flow. This powerful synergy addresses key challenges in agent-to-agent (A2A) communication, interaction with external resources, and the overall stability and observability of complex multi-agent environments.

Summarize with AI: ChatGPT Claude Google AI Mode Grok Perplexity In today’s data-driven world, business intelligence and analytics play a huge role in better understanding your customers, improving your operations, and making actionable business decisions. While there’s no doubt about the value of implementing a BI solution, many ERP users face the same challenges around the quality and credibility of their data.

In our previous blog post, we introduced two ways that Confluent Cloud can integrate with AWS Lambda. One option is using Lambda’s Event Source Mapping (ESM) for Apache Kafka, wherein Lambda creates a consumer group, consumes records off the provided topic, and triggers the Lambda function. The record is polled by the ESM, and the consumed record subsequently acts as the event data provided to (and processed by) the Lambda function.

Enterprise data storage comprises a patchwork of systems: ERP databases, CRM platforms, spreadsheets, cloud apps, and legacy files. These systems do their own jobs well individually, but collectively they create a fragmented landscape. For anyone tasked with building a migration, an integration, or even a simple report, the first challenge is not moving data. It’s understanding what exists and how it all connects.