List of Apache BookKeeper Customers
Wilmington, 19801, DE,
United States
Since 2010, our global team of researchers has been studying Apache BookKeeper customers around the world, aggregating massive amounts of data points that form the basis of our forecast assumptions and perhaps the rise and fall of certain vendors and their products on a quarterly basis.
Each quarter our research team identifies companies that have purchased Apache BookKeeper for Servers, Storage and Networking from public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources, including the customer size, industry, location, implementation status, partner involvement, LOB Key Stakeholders and related IT decision-makers contact details.
Companies using Apache BookKeeper for Servers, Storage and Networking include: Twitter, Inc., a United States based Media organisation with 7500 employees and revenues of $5.08 billion, Splunk, a United States based Professional Services organisation with 8000 employees and revenues of $3.75 billion, Yahoo, a United States based Media organisation with 7000 employees and revenues of $1.80 billion and many others.
Contact us if you need a completed and verified list of companies using Apache BookKeeper, including the breakdown by industry (21 Verticals), Geography (Region, Country, State, City), Company Size (Revenue, Employees, Asset) and related IT Decision Makers, Key Stakeholders, business and technology executives responsible for the software purchases.
The Apache BookKeeper customer wins are being incorporated in our Enterprise Applications Buyer Insight and Technographics Customer Database which has over 100 data fields that detail company usage of software systems and their digital transformation initiatives. Apps Run The World wants to become your No. 1 technographic data source!
Apply Filters For Customers
| Logo | Customer | Industry | Empl. | Revenue | Country | Vendor | Application | Category | When | SI | Insight |
|---|---|---|---|---|---|---|---|---|---|---|---|
 |
Splunk | Professional Services | 8000 | $3.8B | United States | Apache Software | Apache BookKeeper | Servers, Storage and Networking | 2019 | n/a |
In 2019, Splunk integrated Apache BookKeeper into its streaming stack after acquiring Streamlio and embedding Pulsar-related streaming technology into Splunk Data Stream Processor. Category: The integration is described as supporting real-time telemetry, routing and observability use cases globally, with Apache BookKeeper inferred to provide the persistent message storage layer that underpins the Pulsar components adopted into Splunk Data Stream Processor.
Deployment concentrated on instrumenting durable log storage for event streams inside Splunk Data Stream Processor, aligning BookKeeper ledger and journal concepts with the platform's streaming ingestion and routing pipelines. The work impacted engineering and observability product teams, and required configuration of BookKeeper storage conventions, client write and read paths and Pulsar protocol handlers to ensure end-to-end streaming persistence and routing governance across Splunk's platform.
|
 |
Twitter, Inc. | Media | 7500 | $5.1B | United States | Apache Software | Apache BookKeeper | Servers, Storage and Networking | 2015 | n/a |
In 2015, Twitter, Inc. deployed Apache BookKeeper to underpin durable event streaming infrastructure. Apache BookKeeper Apps Category: was used together with DistributedLog to construct a durable real time data pipeline for search ingestion, transactional services, and real time analytics in the United States.
The implementation emphasized low write latencies and high durability for streaming workloads, leveraging Apache BookKeeper ledger based storage and replication semantics to persist ordered event streams. Apache BookKeeper served as the durable storage layer for DistributedLog, providing append and replication capabilities to support ingestion and transactional write paths and to maintain ordered persistence for downstream analytics.
Operational coverage included Twitter search ingestion, transactional service backends, and real time analytics teams, and the deployment is documented in Twitter engineering talks and writeups that describe BookKeeper plus DistributedLog in production. Governance and operational practices referenced in public documentation focused on production monitoring, storage replication policies, and runbooks for operating BookKeeper clusters in support of streaming and transactional workflows.
|
 |
Yahoo | Media | 7000 | $1.8B | United States | Apache Software | Apache BookKeeper | Servers, Storage and Networking | 2015 | n/a |
In 2015, Yahoo and Verizon Media adopted Apache BookKeeper as the durable storage layer for large-scale real time messaging and streaming, Apps Category: . The decision positioned Apache BookKeeper as the persistent store supporting content and advertising platforms across properties operating in the United States.
Apache BookKeeper was deployed as a distributed ledger based persistent store, operating clusters of bookie nodes to provide durable, low latency append only storage for event streams. Implementation details inferred from usage indicate BookKeeper served as the storage layer beneath Apache Pulsar, integrating with Pulsar broker and client tiers to persist trillions of records and to sustain multi petabyte daily throughput in production.
Operational scope centered on real time messaging and streaming workloads supporting content delivery and advertising systems, with production cluster operations, capacity planning, and data retention policies forming the primary governance controls. The deployment emphasized ledger replication and durable write configurations to meet the persistence and latency characteristics required by Yahoo and Verizon Media streaming pipelines.
|
Buyer Intent: Companies Evaluating Apache BookKeeper
Discover Software Buyers actively Evaluating Enterprise Applications
| Logo | Company | Industry | Employees | Revenue | Country | Evaluated | ||
|---|---|---|---|---|---|---|---|---|
| No data found | ||||||||