G2

Anup M.

Engineering Manager

Mid-Market (51-1000 emp.)

8/11/2023

"seamless experience"

5/5

What do you like best about Confluent?

Smooth integration, and resilence aThe best part is that it removes the operational burden of running Kafka ourselves. We use Kafka as the backbone for subscription lifecycle events — membership state transitions, billing events, feature-specific event streams — and with Confluent we get elastic, fully managed clusters without dedicating engineering time to broker management, partition rebalancing, or upgrade cycles. For a lean distributed team, not having a Kafka ops rotation is a genuine capacity win.nd stability. Review collected by and hosted on G2.com.

What do you dislike about Confluent?

Debugging tooling in the console is limited. Inspecting messages on a topic, tracing a specific event through the system, or answering "did this event actually get produced, and who consumed it" still means reaching for CLI tools or custom consumers. For a platform this mature, message browsing and search in the UI feel underpowered. Review collected by and hosted on G2.com.

What problems is Confluent solving and how is that benefiting you?

Confluent solves the problem of running reliable event streaming infrastructure without owning Kafka operations. Our subscription business runs on lifecycle events — membership state transitions, billing and payment events, feature-specific streams like saved-hours tracking — and multiple services plus analytics pipelines depend on those events being durable, ordered, and available. Confluent gives us that backbone as a managed service. Review collected by and hosted on G2.com.