Azure Event Hubs VS Confluent

We're looking into some sort of cloud-based solution to route our Palo Alto firewall logs to across our customer base. I'm with an MSP that manages over a hundred PA firewalls. I was intrigued by the Event Hubs (https://azure.microsoft.com/en-us/products/event-hubs/) solution as a way to push logs to it and then ingest them from there into our SIEM, without having to deal with challenges of multi-tenancy and... Source: over 1 year ago

Microsoft released Azure Stream Analytics no-code editor, a drag-and-drop canvas for developing jobs for stream processing scenarios such as streaming ETL, ingestion, and materializing data to data into general availability. The no-code editor is hosted in the company’s big-data streaming platform and event ingestion service, Azure Event Hubs. Interestingly, the offering follows up after Confluent's recent release... Source: over 1 year ago

Sometimes you don’t need an entire Java-based microservice. You can build serverless APIs with the help of Azure Functions. For example, Azure functions have a bunch of built-in connectors like Azure Event Hubs to process event-driven Java code and send the data to Azure Cosmos DB in real-time. FedEx and UBS projects are great examples of real-time, event-driven Java. I also recommend you to go through 👉 Code,... - Source: dev.to / over 1 year ago

For event infrastructure, we have a bunch of options, like Azure Service Bus, Azure Event Grid and Azure Event Hubs. Like the databases, they aren't mutually exclusive and I could use all, depending on the circumstance, but to keep things simple, I'll pick one and move on. Right now I'm more inclined towards Event Hubs, as it works similarly to Apache Kafka, which is a good fit for the presentation context. - Source: dev.to / about 3 years ago

We’re going to setup a Kafka cluster using confluent.io, create a producer and consumer as well as enhance our behavior driven tests to include the new interface. We’re going to update our helm chart so that the updates are seamless to Kubernetes and we’re going to leverage our observability stack to propagate the traces in the published messages. Source: about 2 years ago