We use Confluent for managing Kafka. We utilize it extensively across all teams in our organization.

We use the product to store and govern the data.

The solution is being used for data integration. 

It is used for various aspects of software development and documentation, including requirements gathering, and testing - both functional and unit, as well as managing customer-generated tickets. It is also employed for ticket resolution, defining software requirements, and aiding in software development planning. For the planning aspects, it is often integrated with Jira, a popular project management and issue-tracking tool. It also plays a role in defining and executing software workflows triggered by Jira tickets, ensuring that necessary activities are carried out efficiently and in a structured manner.

The solution is used for data pipelines.

Since Confluent is integrated with Jira, we use it to keep our key documentation, including product development and LLD design documents. We also use Confluent to support or track the progress of the different work items spent or released.

We use the solution for wiki to share information with the spaces. For example, we have an idea that supports the developer team, so we create spaces to share the documentation. We have access to some data.

We use it for internal communication. Before Confluent, we shared documentation through our work. But with Confluent, we simply create different folders for different purposes. 

It's very easy. I can create a page and share it with others. For development, we use the "one way to page" key point feature, which makes development super easy and quick.

Another interesting aspect is that multiple people can modify the same page simultaneously. If you click edit, you'll see other people's initials moving around. It's quite funny.

Within our organization, Confluence serves as a versatile tool for managing internal human resources, overseeing processes, automating office tasks, publishing content, and handling a wide range of other tasks.

Our primary use case for this solution is processing vast chunks of data in real-time. We deploy the solution on cloud.

We primarily use Confluent for service desk and task management. It is also good for knowledge base management.

Our company has a wide portfolio of use cases in which we recently changed the entire landscape. We use Confluent to share useable dat across all portfolios through a central place.

We use dedicated clusters with four CKs. On standard clusters we are using just the standard configurations that comes out of the box in Confluent Cloud.

We collect service log data with Confluent and use it for fraud detection in game services.

I work in the insurance domain. We stream data in and out Confluent. If financial data is being used most organizations prefer to stay on-premise with their data, but there is a cloud version available. These are the features that Confluent provides.

We're currently working on one of our largest implementations with 500 billion-plus records in real-time and 100 billion on a daily basis. The client aggregates the reports. I'm a solution architect and we are customers of Confluent. 

We use Apache Kafka and Confluent Cloud to stream event data from APIs and work with CDC log data from databases for data integration.

I use the tool to create documentation that needs particular specifications.

We are using Confluent for the basic use cases of messaging. For example, creating a topic and posting the events on the topic.

Our use cases include data streaming, enterprise architecture, integrations, and complete data saving needs, some AI workloads, and standardization. We work on all of these.

We are providing the solution for real-time data for the banking sector.

I use Confluent for real-time data processing and ETL tasks.

We are using Confluent for documentation. We use it to have documentation for the Agile team, as a reference or to share it with the stakeholders. It holds the project data, and what's happening right now. 

At a higher level, the business initiative and all things related to tracking high-level, enterprise-level tasks is something we are not doing it right now. We are doing that part in a very traditional way using Excel sheets, which is very manual work. We haven't automated it yet. 

Confluent is an amazing tool. It gives you the ability to basically create nice documentation for various products. It is highly configurable and integrates very well with Jira. You can use it for reporting as well. When it comes to hosting online content, it is in competition with SharePoint.