Confluent

““The revenue boost is huge because we free our teams to go work on more real-time use cases.””

““I was able to make some back-of-the-envelope calculations, to show how much running three clusters in MSK was costing us a day, and contrast that with our costs in Confluent Cloud. And the Confluent cost was about the same—or a little cheaper in some instances—but my management overhead was so drastically reduced with Confluent that it immediately showed value from a total cost of ownership perspective.””

““It’s super fast because it’s binary messages and we don’t have to do any filtering at all. We’re getting the performance we want without having to worry about tweaking anything, which is really nice.””

““Confluent’s fully managed Amazon S3 connector enables teams to focus on development work by removing the operational burden and risk of managing and maintaining these connectors on their own.””

““Our prior system, RabbitMQ, wasn’t able to scale. With Confluent, we can scale seamlessly and deploy from Confluent’s connector portfolio instead of building connectors on our own.””

“"It’s amazing how much more we can get done when we don’t have to worry about exactly how to do things. We can trust Confluent to offer a secure and rock-solid Kafka platform with a myriad of value-add capabilities like security, connectors, and stream governance on top."”

“We’re a search product for artists and other types of people who need certain types of footage quickly, so obviously our search algorithm is fundamental to our business. We wouldn’t be able to iterate on our search algorithm as quickly as we can now if we didn’t have Confluent as that central data bus. We’re now able to easily collect all of the search data where people hover over and download the videos, so the user search experience in 2022 will be greatly improved as we begin to use more machine learning.”

“One of the most noteworthy benefits of using Confluent for us has been for our rebranding project, which was the end result of our microservices project to consolidate all of our services into one Storyblocks.com where users could search videos and audio in the same place. Users used to have to log in to two different sites and now they can just log in to one site and get access to the audio and video in one place. Confluent was a big part of this.”

“The infinite retention is important because analysts sometimes look at historical data when answering various questions for the business; I’ll bet that at some point in the next six months some squad or team in the business has new questions about our content contributors’ historical behavior, and an analyst will ask to dig into our content service events.”

“For us, just having one way of communicating was game-changing,” says Charles DeVeas, Director of Engineering, Storyblocks. “Having the one event pipeline that’s flexible for everyone’s use case that we can use to communicate or to absorb data, that’s amazing.”

“Confluent is definitely the central pillar of our data infrastructure. All data collection that isn’t an application database is going on our central pipeline through Confluent.”

“"Not everyone needs every event," says Sözeri. "Flink helps us deliver exactly what each operation needs, including late event handling and deduplication."”

“"This reduces latency and load dramatically," Sözeri explains. "We don't call inventory and pricing services on every request anymore. Reads are local and consistent."”

“"Fully managed Kafka lets our teams focus on event contracts and product work, not operations," Sözeri explains. "We needed to cut undifferentiated operations – capacity upgrades, cluster hygiene, connector glue and schema registry."”

“"It only took one year to see the big results – faster app, lower costs, more stability, and teams could finally move at their own speed."”

“Jenius is powered in part by Confluent, with asynchronous transactions flowing over Kafka topics. Going forward, we plan to enhance our fraud detection system by linking it directly into these same topics.”

“Now, with Confluent and ksqlDB we can perform enrichment midstream on Kafka topics, which eliminates the need to develop and maintain a separate microservice, simplifies our environment, and enables us to optimize the use of our resources.”

“With Confluent, we have implemented a system in which most requests are handled by a cache, reducing the load on our core database and lowering our licensing costs.”

“With Confluent, we have confidence in our Kafka deployment. Confluent engineers not only provide us with support, but they also share with us their deep knowledge of Kafka to help us make the most of our streaming use cases.”

“Confluent is how we ingest all of our data events,”

“(With Confluent), we reduced our projected yearly cost by 69%. And the months of planning we would have to put into meetings and seasonal projections are gone, so our management oversight is reduced from a soft-cost perspective.”

““Confluent is the underlying infrastructure that lets us orchestrate our business logic,” says Hansen. “To be honest, our team mostly takes Kafka for granted these days. We’re not worried about outages, and we know we have an architecture that is easy to work with and will scale as Ladder continues to grow.””

““When we moved from self- managed Kafka to Confluent, we scheduled the switchover at night to be prepared for any issues,” says Hansen. “It turned out not to be necessary; the whole process took all of five minutes, with no downtime for the user.””

““We performed a cost-benefit analysis that took into account how much we were spending to manage Kafka ourselves and how much we lost when it was down,” says Hansen. “It was clear from that analysis that the move to Confluent had paid off quickly.””

““Because we’re no longer spending so much time managing our Kafka cluster, we can focus our engineering resources on what’s important to us as a business: improving the customer experience and improving our underwriting, which drives down costs for our customers,” says Hansen.”