Confluent
每个字节的数据都有一个故事要讲
概述
总部
美国
|
成立年份
2014
|
公司类型
私营公司
|
收入
$10-100m
|
员工人数
201 - 1,000
|
网站
|
推特句柄
|
公司介绍
每一个数据字节都有一个故事要讲,一些重要的事情将告知下一步要做的事情。在数据驱动的企业中,我们如何移动数据变得几乎与数据本身一样重要。随着速度和敏捷性的提高,数据的价值呈指数级增长。
从一开始,我们就将Apache Kafka ® 开源,并使其在数千家公司中获得了令人印象深刻的全行业采用。现在,我们正专注于构建一个事件流平台,以帮助其他公司轻松访问企业数据作为实时流。
物联网解决方案
由Apache Kafka的原始创建者构建的企业事件流平台。
不受限制的开发人员生产力
为更广泛的开发人员普及 Kafka,并加快他们构建事件流应用程序的速度。
大规模高效运营
随着事件流在您的组织中的增长,最大限度地降低操作复杂性,同时确保高性能和可扩展性。
生产阶段的先决条件
使用在生产中实施事件流所需的基本企业级属性来构建平台。
提交者驱动的专业知识
利用世界上最重要的 Kafka 专家,他们直接与 Kafka 提交者合作,在整个应用程序开发生命周期中为您提供帮助。
选择自由
在公有云或混合云中部署本地,从裸机到Kubernetes ,或通过 Confluent Cloud 使用完全托管的云服务
物联网应用简介
Confluent 是平台即服务 (paas)等工业物联网科技方面的供应商。同时致力于金融与保险等行业。
技术栈
Confluent的技术栈描绘了Confluent在平台即服务 (paas)等物联网技术方面的实践。
-
设备层
-
边缘层
-
云层
-
应用层
-
配套技术
技术能力:
无
弱
中等
强
Supplier missing?
Start adding your own!
Register with your work email and create a new supplier profile for your business.
实例探究.

Case Study
Increases the Pace of Digital Deliveries with a Unified Data Platform
Prior to developing the Unified Data Platform, Alight integrated back-end information within a web portal or a mobile app, for example. This approach had several drawbacks, particularly in the areas of performance, cost, and time-to-market for new solutions.They needed to handle large-scale data changes based upon near-time or real-time events in the system so that they could refresh the cache on-demand with subsecond response times.After further research, discussions with partners, vendors, and others in the industry; and some proof-of-concept (POC) projects the team was ready to move forward with their choice: Apache Kafka.

Case Study
Real-Time Contact Center Analytics
Deliver real-time analytics for cloud-based communications services in a mission-critical, multi-tenant environment.As a fast-growing multi-tenant SaaS Contact Center solution, 8×8 needed a way to rapidly and cost-effectively add new customers. To support this, the company decided it wanted a single event streaming platform for all of its customers – one that could scale quickly and easily as new customers joined.The platform needed to be multi-tenant, providing strict data separation – a key customer requirement – and it had to be highly resilient given its mission-critical nature. Robust security was also a must since 8×8 handles sensitive caller information.

Case Study
Greater Independence and a Modern Customer Engagement Strategy
SunPower is building differentiation by creating a software offering for consumers that pairs with their SunPower Equinox® solar and SunVault™ storage systems to give consumers rich access to their own energy usage data, the ability to control their SunVault™ system, and allow SunPower to optimize its own service and offers.However, this requires SunPower to collect, aggregate, and provide access to real-time data from 6 million devices, a significant challenge and well beyond the capabilities of its legacy system.SunPower wanted to utilize the vast amount of data it generated on energy usage across its existing fleet to build more efficient products, make data more accessible and actionable by different parts of the business, and offer customers a more instantaneous energy management experience.

Case Study
Redesign Data Pipeline and Slash Technical Debt
As the company transitioned from a scrappy disruptor to a major industry player, it began to experience issues with a monolithic application it had built when the company was started. They also experienced other issues later with synchronous REST API calls between services, after they had split the monolith into microservices.Namely, developers and data engineers couldn’t resolve issues fast enough or iterate on their search functionality with sufficient agility and were taking on a significant amount of technical debt as an increasing amount of data threatened to slow down the productivity and time to market for new features.The challenge is to create an event bus to improve data collection, event-driven communication between microservices, and data discovery for new use cases.