[{"data":1,"prerenderedAt":2164},["ShallowReactive",2],{"active-banner":3,"navbar-featured-partner-blog":24,"navbar-pricing-featured":306,"blog-\u002Fblog\u002Fapache-pulsar-2-6-0":1086,"blog-authors-\u002Fblog\u002Fapache-pulsar-2-6-0":2129,"related-\u002Fblog\u002Fapache-pulsar-2-6-0":2146},{"id":4,"title":5,"date":6,"dismissible":7,"extension":8,"link":9,"link2":10,"linkText":11,"linkText2":12,"meta":13,"stem":21,"variant":22,"__hash__":23},"banners\u002Fbanners\u002Flakestream-ufk-launch.md","StreamNative Introduces Lakestream Architecture and Launches Native Kafka Service","2026-04-07",true,"md","\u002Fblog\u002Ffrom-streams-to-lakestreams","https:\u002F\u002Fconsole.streamnative.cloud\u002Fsignup?from=banner_lakestream-launch","Read Announcement","Sign Up Now",{"body":14},{"type":15,"value":16,"toc":17},"minimark",[],{"title":18,"searchDepth":19,"depth":19,"links":20},"",2,[],"banners\u002Flakestream-ufk-launch","default","zRueBGutATZB0ZnFFHwaEV7F0Di4tnZUHhgOiI4cu6k",{"id":25,"title":26,"authors":27,"body":29,"category":289,"createdAt":290,"date":291,"description":292,"extension":8,"featured":7,"image":293,"isDraft":294,"link":290,"meta":295,"navigation":7,"order":296,"path":297,"readingTime":298,"relatedResources":290,"seo":299,"stem":300,"tags":301,"__hash__":305},"blogs\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025.md","StreamNative Recognized as a Contender in The Forrester Wave™: Streaming Data Platforms, Q4 2025",[28],"David Kjerrumgaard",{"type":15,"value":30,"toc":276},[31,39,47,51,67,73,78,81,87,102,109,115,118,124,127,134,140,143,146,157,163,169,172,175,178,184,191,194,197,204,207,210,224,229,233,237,241,245,249,251,268,270],[32,33,35],"h3",{"id":34},"receives-highest-possible-scores-in-both-the-messaging-and-resource-optimization-criteria",[36,37,38],"em",{},"Receives Highest Possible Scores in BOTH the Messaging and Resource Optimization Criteria",[40,41,43],"h2",{"id":42},"introduction",[44,45,46],"strong",{},"Introduction",[48,49,50],"p",{},"Real-time data has become the backbone of modern innovation. As artificial intelligence (AI) and digital services demand instantaneous insights, organizations are realizing that streaming data is no longer optional – it's essential for delivering timely, context-rich experiences. StreamNative's data streaming platform is built precisely for this reality, ensuring data is immediate, reliable, and ready to power critical applications.",[48,52,53,54,63,64],{},"Today, we're excited to announce that Forrester Research has named StreamNative as a Contender in its evaluation, ",[55,56,58],"a",{"href":57},"\u002Freports\u002Frecognized-in-the-forrester-wave-tm-streaming-data-platforms-q4-2025",[36,59,60],{},[44,61,62],{},"The Forrester Wave™: Streaming Data Platforms, Q4 2025",". This report evaluated 15 top streaming data platform providers, and we're proud to share that ",[44,65,66],{},"StreamNative received the highest scores possible—5 out of 5—in both the Messaging and Resource Optimization criteria.",[48,68,69,70],{},"***Forrester's Take: ***",[36,71,72],{},"\"StreamNative is a good fit for enterprises that want an Apache Pulsar implementation that is also compatible with Kafka APIs.\"",[48,74,75],{},[36,76,77],{},"— The Forrester Wave™: Streaming Data Platforms, Q4 2025",[48,79,80],{},"Being recognized in the Forrester Wave is a proud milestone, and for us, it highlights how far StreamNative has come in enabling enterprises to unlock the power of real-time data. In the sections below, we'll dive into what we believe sets StreamNative apart—from our modern architecture and cloud-native design to our open-source foundation and real-time use cases—and how we see these strengths aligning with Forrester's findings.",[40,82,84],{"id":83},"trusted-by-industry-leaders",[44,85,86],{},"Trusted by Industry Leaders",[48,88,89,90,93,94,97,98,101],{},"Companies across industries are already leveraging StreamNative to drive real-time outcomes. Global enterprises like ",[44,91,92],{},"Cisco"," rely on StreamNative to handle massive IoT telemetry, supporting 245 million+ connected devices. Martech leaders such as ",[44,95,96],{},"Iterable"," process billions of events per day with StreamNative for hyper-personalized customer engagement. And in financial services, ",[44,99,100],{},"FICO"," trusts StreamNative to power its real-time fraud detection and analytics pipelines with a secure, scalable streaming backbone.",[48,103,104,105,108],{},"The Forrester report notes that, “",[36,106,107],{},"Customers appreciate the lower infrastructure costs that result from StreamNative’s cost-efficient, Kafka-compatible architecture. Customers note excellent support responsiveness…","”",[40,110,112],{"id":111},"modern-cloud-native-architecture-built-for-scale",[44,113,114],{},"Modern, Cloud-Native Architecture Built for Scale",[48,116,117],{},"From day one, StreamNative was designed with a modern architecture to meet the demanding scale and flexibility requirements of real-time data. Unlike legacy streaming systems that often rely on tightly coupled storage and compute, StreamNative's platform takes a cloud-native approach: it decouples these layers to enable elastic scalability and efficient resource utilization across any environment. The core is powered by Apache Pulsar—a distributed messaging and streaming engine—enhanced with multi-protocol support (including native Apache Kafka API compatibility) to unify diverse data streams under one roof. This means organizations can consolidate siloed messaging systems and handle both high-volume event streams and traditional message queues on a single platform, without sacrificing performance or reliability.",[48,119,120,121,108],{},"Forrester's evaluation described that “",[36,122,123],{},"StreamNative aims to provide a high-performance, multi-protocol streaming data platform: It uses Apache Pulsar with Kafka API compatibility to deliver cost-efficient, real-time applications for enterprises. It appeals to organizations that want a flexible, low-cost streaming solution, due to its focus on scalability and resource optimization, while its investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.",[48,125,126],{},"Our cloud-first, leaderless architecture (with no single broker bottlenecks) and tiered storage model were built to maximize throughput and cost-efficiency for real-time workloads. By separating compute from storage and leveraging distributed object storage, StreamNative can retain huge volumes of event data indefinitely while keeping compute costs in check—effectively providing a flexible, low-cost streaming solution.",[48,128,129,130,133],{},"This modern design not only delivers high performance, but also ensures fault tolerance and geo-distribution out of the box, so enterprises can trust their streaming data is always available and durable. As Forrester’s evaluation noted, StreamNative ",[36,131,132],{},"\"excels at messaging and resource optimization\" and “Its platform supports use cases like real-time analytics and event-driven architectures with robust scalability.","” Our architecture provides the strong foundation that today's real-time applications demand, from ultra-fast data ingestion to seamless scale-out across hybrid and multi-cloud environments.",[40,135,137],{"id":136},"open-source-foundation-and-pulsar-expertise",[44,138,139],{},"Open Source Foundation and Pulsar Expertise",[48,141,142],{},"StreamNative's DNA is rooted in open source innovation. Our founders are the original creators of Apache Pulsar, and we've built our platform with the same open principles: freedom, flexibility, and community-driven innovation. For developers and data teams, this means adopting StreamNative comes with no proprietary lock-in—instead, you get a platform built on open standards and a thriving ecosystem. We offer broad API compatibility (Pulsar, Kafka, JMS, MQTT, and more) so that teams can work with familiar interfaces and integrate StreamNative into existing systems with ease.",[48,144,145],{},"StreamNative is the primary commercial contributor to the Apache Pulsar project and its surrounding ecosystem. We invest heavily in Pulsar's ongoing improvements our investments in Pulsar's open-source ecosystem and performance optimization bolster StreamNative's value. We also foster a vibrant community through initiatives like the Data Streaming Summit and free training resources.",[48,147,148,149,152,153,156],{},"Forrester's assessment noted that StreamNative’s “",[36,150,151],{},"events-driven agents, extensibility, and performance architecture are solid,","” and we're continuing to build on that foundation. ",[44,154,155],{},"We're actively investing in expanding our tooling for observability, governance, schema management, and developer productivity","—areas we recognize as critical for enterprise adoption and where we're committed to accelerating our roadmap.",[48,158,159,160],{},"Being open also means embracing an open ecosystem of technologies. StreamNative actively integrates with the tools and platforms that matter most to our users. We partner with industry leaders like Snowflake, Databricks, Google, and Ververica to ensure our streaming platform works seamlessly with data warehouses, lakehouse storage, and stream processing frameworks. Forrester’s evaluation observed that StreamNative’s ",[36,161,162],{},"\"investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.\"",[40,164,166],{"id":165},"powering-real-time-use-cases-across-industries",[44,167,168],{},"Powering Real-Time Use Cases Across Industries",[48,170,171],{},"One of the greatest validations of StreamNative's approach is the success our customers are achieving with real-time data. StreamNative's platform is versatile and use-case agnostic—if an application demands high-volume, low-latency data movement, we can power it. This flexibility is why our customer base spans industries from finance and IoT to major automobile manufacturers and online gaming. The common thread is that these organizations need to process and react to data in milliseconds, and StreamNative is delivering the capabilities to make that possible.",[48,173,174],{},"Cisco uses StreamNative to underpin an IoT telemetry system of colossal scale, connecting hundreds of millions of devices and thousands of enterprise clients with real-time data streams. The platform's multi-tenant design and proven reliability allow Cisco to offer its customers a live feed of device data with unwavering confidence. In the financial sector, FICO has built streaming pipelines on StreamNative to detect fraud as transactions happen and to monitor systems in real time. With StreamNative's strong guarantees around message durability and ordering, FICO can catch anomalies or suspicious patterns within seconds. And in digital customer engagement, Iterable relies on StreamNative to process billions of events every day—clicks, views, purchases—so that marketers can trigger personalized campaigns instantly based on user behavior.",[48,176,177],{},"Our customers uniformly deal with mission-critical data streams, where downtime or delays are unacceptable. StreamNative's fault-tolerant, scalable infrastructure has proven equal to the task, handling scenarios like bursting to millions of events per second or seamlessly spanning multiple cloud regions. Forrester's report recognized StreamNative for supporting event-driven architectures with robust scalability—which for us is a reflection of our platform's ability to meet the most demanding enterprise requirements.",[40,179,181],{"id":180},"continuing-to-innovate-ursa-orca-and-the-road-ahead",[44,182,183],{},"Continuing to Innovate: Ursa, Orca, and the Road Ahead",[48,185,186,187,190],{},"While we are thrilled to be recognized in Forrester's Streaming Data Platforms Wave, we view this as just the beginning. StreamNative's vision has always been bold: to ",[44,188,189],{},"provide a unified platform that not only handles today's streaming needs but also anticipates the emerging requirements of tomorrow",".",[48,192,193],{},"One key area of focus is the convergence of streaming data with advanced analytics and AI. As Forrester points out in the report, technology leaders should look for platforms that natively integrate messaging, stream processing, and analytics to provide AI agents with real-time, contextualized information. We couldn't agree more. Our award-winning Ursa Engine and Orca Agent Engine are aimed at extending our platform up the stack—bridging the gap between data streams and data lakes, and between event streams and intelligent processing.",[48,195,196],{},"Our new Ursa Engine introduces a lakehouse-native approach to streaming: it can write events directly to table formats like Iceberg on cloud storage, eliminating entire classes of ETL jobs and making fresh data instantly available for analytics queries. By integrating streaming and lakehouse technologies, we help customers collapse data silos and accelerate their AI\u002FML pipelines.",[48,198,199,200,203],{},"Beyond analytics integration, we are also enhancing StreamNative with more out-of-the-box processing and governance capabilities. In the coming months, we plan to introduce new features for lightweight stream processing and transformation, making it easier to build reactive applications directly on the platform. We're also expanding our ecosystem of connectors and integrations, so that whether your data lands in Snowflake, Databricks, or an AI model, StreamNative will seamlessly feed it. ",[44,201,202],{},"We're investing significantly in enterprise features including security, schema registry, governance, and monitoring tooling","—capabilities that are essential for mission-critical deployments and where we're committed to continued improvement.",[48,205,206],{},"This recognition from Forrester energizes us to keep innovating at full speed. We're sharing this honor with our amazing customers, community, and partners who drive us forward every day. Your feedback and real-world challenges have helped shape StreamNative into what it is today, and together, we will shape the future of streaming data. Thank you for joining us on this journey—we're just getting started, and we can't wait to deliver even more value as we continue to evolve our platform. Onward to real-time everything!",[208,209],"hr",{},[32,211,213],{"id":212},"streamnative-in-the-forrester-wave-evaluation-findings",[44,214,215,216,223],{},"StreamNative in ",[44,217,218],{},[55,219,220],{"href":57},[44,221,222],{},"The Forrester Wave™",": Evaluation Findings",[225,226,228],"h5",{"id":227},"recognized-as-a-contender-among-15-streaming-data-platform-providers","• Recognized as a Contender among 15 streaming data platform providers",[225,230,232],{"id":231},"received-the-highest-scores-possible-50-in-both-the-messaging-and-resource-optimization-criteria","* Received the highest scores possible (5.0) in both the Messaging and Resource Optimization criteria",[225,234,236],{"id":235},"cited-as-the-primary-platform-for-enterprises-wishing-to-implement-pulsar","• Cited as the primary platform for enterprises wishing to implement Pulsar",[225,238,240],{"id":239},"noted-for-excelling-at-messaging-and-resource-optimization","• Noted for excelling at messaging and resource optimization",[225,242,244],{"id":243},"customers-cited-lower-infrastructure-costs-and-excellent-support-responsiveness","• Customers cited lower infrastructure costs and excellent support responsiveness",[225,246,248],{"id":247},"recognized-for-supporting-event-driven-architectures-with-robust-scalability","• Recognized for supporting event-driven architectures with robust scalability",[208,250],{},[252,253,255,256,259,260,190],"h6",{"id":254},"forrester-disclaimer-forrester-does-not-endorse-any-company-product-brand-or-service-included-in-its-research-publications-and-does-not-advise-any-person-to-select-the-products-or-services-of-any-company-or-brand-based-on-the-ratings-included-in-such-publications-information-is-based-on-the-best-available-resources-opinions-reflect-judgment-at-the-time-and-are-subject-to-change-for-more-information-read-about-forresters-objectivity-here","**Forrester Disclaimer: **",[36,257,258],{},"Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change",". *For more information, read about Forrester’s objectivity *",[55,261,265],{"href":262,"rel":263},"https:\u002F\u002Fwww.forrester.com\u002Fabout-us\u002Fobjectivity\u002F",[264],"nofollow",[36,266,267],{},"here",[208,269],{},[252,271,273],{"id":272},"apache-apache-pulsar-apache-kafka-apache-flink-and-other-names-are-trademarks-of-the-apache-software-foundation-no-endorsement-by-apache-or-other-third-parties-is-implied",[36,274,275],{},"Apache®, Apache Pulsar®, Apache Kafka®, Apache Flink® and other names are trademarks of The Apache Software Foundation. No endorsement by Apache or other third parties is implied.",{"title":18,"searchDepth":19,"depth":19,"links":277},[278,280,281,282,283,284,285],{"id":34,"depth":279,"text":38},3,{"id":42,"depth":19,"text":46},{"id":83,"depth":19,"text":86},{"id":111,"depth":19,"text":114},{"id":136,"depth":19,"text":139},{"id":165,"depth":19,"text":168},{"id":180,"depth":19,"text":183,"children":286},[287],{"id":212,"depth":279,"text":288},"StreamNative in The Forrester Wave™: Evaluation Findings","Company",null,"2025-12-16","StreamNative is recognized in The Forrester Wave™: Streaming Data Platforms, Q4 2025. Discover why Forrester highlights StreamNative's high-performance messaging, efficient resource use, and cost-effective Kafka API compatibility for real-time innovation.","\u002Fimgs\u002Fblogs\u002F693bd36cf01b217dcb67278f_Streamnative_blog_thumbnail.png",false,{},0,"\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025","10 mins read",{"title":26,"description":292},"blog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025",[302,303,304],"Announcements","Real-Time","Forrester","sOeeJtEO3O-IIfTPJjY1AFOMawZ_rf8FOH8A98NEKgU",{"id":307,"title":308,"authors":309,"body":314,"category":1073,"createdAt":290,"date":1074,"description":1075,"extension":8,"featured":7,"image":1076,"isDraft":294,"link":290,"meta":1077,"navigation":7,"order":296,"path":1078,"readingTime":1079,"relatedResources":290,"seo":1080,"stem":1081,"tags":1082,"__hash__":1085},"blogs\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour.md","How We Run a 5 GB\u002Fs Kafka Workload for Just $50 per Hour",[310,311,312,313],"Matteo Meril","Neng Lu","Hang Chen","Penghui Li",{"type":15,"value":315,"toc":1043},[316,319,322,325,328,331,335,338,348,354,357,365,370,374,381,384,387,395,399,402,407,411,414,417,420,423,432,436,439,450,453,457,460,463,474,477,481,485,493,496,500,508,537,541,544,549,553,556,560,563,566,571,580,585,588,591,602,606,609,620,624,627,630,635,638,667,671,673,679,682,687,692,695,699,713,717,728,732,747,756,767,770,773,777,780,783,794,797,800,803,808,813,817,821,838,842,856,861,865,876,879,895,899,910,915,920,928,932,935,939,946,950,953,962,967,976,982,991,1000,1009,1018,1027,1035],[48,317,318],{},"The rise of DeepSeek has shaken the AI infrastructure market, forcing companies to confront the escalating costs of training and deploying AI models. But the real pressure point isn’t just compute—it’s data acquisition and ingestion costs.",[48,320,321],{},"As businesses rethink their AI cost-containment strategies, real-time data streaming is emerging as a critical enabler. The growing adoption of Kafka as a standard protocol has expanded cost-efficient options, allowing companies to optimize streaming analytics while keeping expenses in check.",[48,323,324],{},"Ursa, the data streaming engine powering StreamNative’s managed Kafka service, is built for this new reality. With its leaderless architecture and native lakehouse storage integration, Ursa eliminates costly inter-zone network traffic for data replication and client-to-broker communication while ensuring high availability at minimal operational cost.",[48,326,327],{},"In this blog post, we benchmarked the infrastructure cost and total cost of ownership (TCO) for running a 5GB\u002Fs Kafka workload across different Kafka vendors, including Redpanda, Confluent WarpStream, and AWS MSK. Our benchmark results show that Ursa can sustain 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda—making it the ideal solution for high-performance, cost-efficient ingestion and data streaming for data lakehouses and AI workloads.",[48,329,330],{},"Note: We also evaluated vanilla Kafka in our benchmark; however, for simplicity, we have focused our cost comparison on vendor solutions rather than self-managed deployments. That said, it is important to highlight that both Redpanda and vanilla Kafka use a leader-based data replication approach. In a data-intensive, network-bound workload like 5GB\u002Fs streaming, with the same machine type and replication factor, Redpanda and vanilla Kafka produced nearly identical cost profiles.",[40,332,334],{"id":333},"key-benchmark-findings","Key Benchmark Findings",[48,336,337],{},"Ursa delivered 5 GB\u002Fs of sustained throughput at an infrastructure cost of just $54 per hour. For comparison:",[339,340,341,345],"ul",{},[342,343,344],"li",{},"MSK: $303 per hour → 5.6x more expensive compared to Ursa",[342,346,347],{},"Redpanda: $988 per hour → 18x more expensive compared to Ursa",[48,349,350],{},[351,352],"img",{"alt":18,"src":353},"\u002Fimgs\u002Fblogs\u002F679c71b67d9046f26edc7977_AD_4nXfvTqyBNUBu2lObdkKAx-5UNkpNP8UYULLZyOcixE6z99VMZUUEsUqWjzexI7vjyNGRNSAUoM9smYvdTP55ctAhIbrs5lmQgcSVMWdaoigbWouCl95DVSQsxooY-qqfGcYqS4g4zA.png",[48,355,356],{},"Beyond infrastructure costs, when factoring in both storage pricing, vendor pricing and operational expenses, Ursa’s total cost of ownership (TCO) for a 5GB\u002Fs workload with a 7-day retention period is:",[339,358,359,362],{},[342,360,361],{},"50% cheaper than Confluent WarpStream",[342,363,364],{},"85% cheaper than MSK and Redpanda",[48,366,367],{},[351,368],{"alt":18,"src":369},"\u002Fimgs\u002Fblogs\u002F679c602d77e9c706de5343b8_AD_4nXeDv8rrv_C1CTCCiqYo1zpvlGYbdBk1r0VEqovAPu22iFMQZgh54Hfw9PBMLzM7jDFxKwAFDxbdG0np4XVk_tGsWhEKMloLRcmmea7lvueCx-0cFsyaE3Mya4Mxc1Dox95A6JEc.png",[40,371,373],{"id":372},"ursa-highly-cost-efficient-data-streaming-at-scale","Ursa: Highly Cost-Efficient Data Streaming at Scale",[48,375,376,380],{},[55,377,379],{"href":378},"\u002Fblog\u002Fursa-reimagine-apache-kafka-for-the-cost-conscious-data-streaming","Ursa"," is a next-generation data streaming engine designed to deliver high performance at a fraction of the cost of traditional disk-based solutions. It is fully compatible with Apache Kafka and Apache Pulsar APIs, while leveraging a leaderless, lakehouse-native architecture to maximize scalability, efficiency, and cost savings.",[48,382,383],{},"Ursa’s key innovation is separating storage from compute and decoupling metadata\u002Findex operations from data operations by utilizing cloud object storage (e.g., AWS S3) instead of costly inter-zone disk-based replication. It also employs open lakehouse formats (Iceberg and Delta Lake), enabling columnar compression to significantly reduce storage costs while maintaining durability and availability.",[48,385,386],{},"In contrast, traditional streaming systems—like Kafka and Redpanda—depend on leader-based architectures, which drive up inter-zone traffic costs due to replication and client communication. Ursa mitigates these costs by:",[339,388,389,392],{},[342,390,391],{},"Eliminating inter-zone traffic costs via a leaderless architecture.",[342,393,394],{},"Replacing costly inter-zone replication with direct writes to cloud storage using open lakehouse formats.",[40,396,398],{"id":397},"how-ursa-eliminates-inter-zone-traffic","How Ursa Eliminates Inter-Zone Traffic",[48,400,401],{},"Ursa minimizes inter-zone traffic by leveraging a leaderless architecture, which eliminates inter-zone communication between clients and brokers, and lakehouse-native storage, which removes the need for inter-zone data replication. This approach ensures high availability and scalability while avoiding unnecessary cross-zone data movement.",[48,403,404],{},[351,405],{"alt":18,"src":406},"\u002Fimgs\u002Fblogs\u002F679c602e21b3571bb7117dca_AD_4nXd7Oahc77NjRLNvA9clLt0tsyU6MrIqVibFYv5pW5giTIcCHPr3EA_yTGzfVEUIVO3VXK56qWK8zmBCp5lY0E_4nmlWIPFrHjtHylA5NhwELjn-UB0fLG2h_kbrxrc7Cs_edvveNA.png",[32,408,410],{"id":409},"leaderless-architecture","Leaderless architecture",[48,412,413],{},"Traditional streaming engines such as Kafka, Pulsar, or RedPanda rely on a leader-based model, where each partition is assigned to a single leader broker that handles all writes and reads.",[48,415,416],{},"Pros of Leader-Based Architectures:\n✔ Maintains message ordering via local sequence IDs\n✔ Delivers low latency and high performance through message caching",[48,418,419],{},"Cons of Leader-Based Architectures:\n✖ Throughput bottlenecked by a single broker per partition\n✖ Inter-zone traffic required for high availability in multi-AZ deployments",[48,421,422],{},"While Kafka and Pulsar offer partial solutions (e.g., reading from followers, shadow topics) to reduce read-related inter-zone traffic, producers still send data to a single leader.",[48,424,425,426,431],{},"Ursa removes the concept of topic ownership, allowing any broker in the cluster to handle reads or writes for any partition. The primary challenge—ensuring message ordering—is solved with ",[55,427,430],{"href":428,"rel":429},"https:\u002F\u002Fgithub.com\u002Fstreamnative\u002Foxia",[264],"Oxia",", a scalable metadata and index service created by StreamNative in 2022.",[32,433,435],{"id":434},"oxia-the-metadata-layer-enabling-leaderless-architecture","Oxia: The Metadata Layer Enabling Leaderless Architecture",[48,437,438],{},"Ensuring message ordering in a leaderless architecture is complex, but Ursa solves this with Oxia:",[339,440,441,444,447],{},[342,442,443],{},"Handles millions of metadata\u002Findex operations per second",[342,445,446],{},"Generates sequential IDs to maintain strict message ordering",[342,448,449],{},"Optimized for Kubernetes with horizontal scalability",[48,451,452],{},"Producers and consumers can connect to any broker within their local AZ, eliminating inter-zone traffic costs while maintaining performance through localized caching.",[32,454,456],{"id":455},"zero-interzone-data-replication","Zero interzone data replication",[48,458,459],{},"In most distributed systems, data replication from a leader (primary) to followers (replicas) is crucial for fault tolerance and availability. However, replication across zones can inflate infrastructure expenses substantially.",[48,461,462],{},"Ursa avoids these costs by writing data directly to cloud storage (e.g., AWS S3, Google GCS):",[339,464,465,468,471],{},[342,466,467],{},"Built-In Resilience: Cloud storage inherently offers high availability and fault tolerance without inter-zone traffic fees.",[342,469,470],{},"Tradeoff: Slightly higher latency (sub-second, with p99 at 500 milliseconds) compared to local disk\u002FEBS (single-digit to sub-100 milliseconds), in exchange for significantly lower costs (up to 10x lower).",[342,472,473],{},"Flexible Modes: Ursa is an addition to the classic BookKeeper-based engine, providing users with the flexibility to optimize for either cost or low latency based on their workload requirements.",[48,475,476],{},"By foregoing conventional replication, Ursa slashes inter-zone traffic costs and associated complexities—making it a compelling option for organizations seeking to balance high-performance data streaming with strict budget constraints.",[40,478,480],{"id":479},"how-we-ran-a-5-gbs-test-with-ursa","How We Ran a 5 GB\u002Fs Test with Ursa",[32,482,484],{"id":483},"ursa-cluster-deployment","Ursa Cluster Deployment",[339,486,487,490],{},[342,488,489],{},"9 brokers across 3 availability zones, each on m6i.8xlarge (Fixed 12.5 Gbps bandwidth, 32 vCPU cores, 128 GB memory).",[342,491,492],{},"Oxia cluster (metadata store) with 3 nodes of m6i.8xlarge, distributed across three availability zones (AZs).",[48,494,495],{},"During peak throughput (5 GB\u002Fs), each broker’s network usage was about 10 Gbps.",[32,497,499],{"id":498},"openmessaging-benchmark-workers-configuration","OpenMessaging Benchmark Workers & Configuration",[48,501,502,503,507],{},"The OpenMessaging Benchmark(OMB) Framework is a suite of tools that make it easy to benchmark distributed messaging systems in the cloud. Please check ",[55,504,505],{"href":505,"rel":506},"https:\u002F\u002Fopenmessaging.cloud\u002Fdocs\u002Fbenchmarks\u002F",[264]," for details.",[339,509,510,525,534],{},[342,511,512,513,518,519,524],{},"12 OMB workers: 6 for ",[55,514,517],{"href":515,"rel":516},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002Fd1094122270775e4f1580947f80c5055",[264],"producers",", 6 for ",[55,520,523],{"href":521,"rel":522},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F06bada89381fb77a7862e1b4c1d8963d",[264],"consumers"," across 3 availability zones, on m6i.8xlarge instances. Each worker is configured with 12 CPU cores and 48 GB memory.",[342,526,527,528,533],{},"Sample YAML ",[55,529,532],{"href":530,"rel":531},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F204c1f26c4d44a218ae235bf2de99904",[264],"scripts"," provided for Kafka-compatible configuration and rate limits.",[342,535,536],{},"Achieved consistent 5 GB\u002Fs publish\u002Fsubscribe throughput.",[40,538,540],{"id":539},"ursa-benchmark-tests-results","Ursa Benchmark Tests & Results",[48,542,543],{},"The following diagram demonstrates that Ursa can consistently handle 5 GB\u002Fs of traffic, fully saturating the network across all broker nodes.",[48,545,546],{},[351,547],{"alt":18,"src":548},"\u002Fimgs\u002Fblogs\u002F679c602d7b261bac1113f7d6_AD_4nXdDPsRc3koXICiFF0bqSmGWbJt_RlUy4FE3ruuWOfbCfpcqZ1dejjqGbkaCJv2hQFL1nirRouBVRW2l5uMWBvY9naMqGB_wHcLI14dBM0f85TXhmdm3UxEv1yGX9Y4hf5FttSkZew.png",[40,550,552],{"id":551},"comparing-infrastructure-cost","Comparing Infrastructure Cost",[48,554,555],{},"This benchmark first evaluates infrastructure costs of running a 5 GB\u002Fs streaming workload (1:1 producer-to-consumer ratio) across different data streaming engines, including Ursa, Redpanda, and AWS MSK, with a focus on multi-AZ deployments to ensure a fair comparison.",[32,557,559],{"id":558},"test-setup-key-assumptions","Test Setup & Key Assumptions",[48,561,562],{},"All tests use multi-AZ configurations, with clusters and clients distributed across three AWS availability zones (AZs). Cluster size scales proportionally to the number of AZs, and rack-awareness is enabled for all engines to evenly distribute topic partitions and leaders.",[48,564,565],{},"To ensure a fair comparison, we selected the same machine type capable of fully utilizing both network and storage bandwidth for Ursa and Redpanda in this 5GB\u002Fs test:",[339,567,568],{},[342,569,570],{},"9 × m6i.8xlarge instances",[48,572,573,574,579],{},"However, MSK's storage bandwidth limits vary depending on the selected instance type, with the highest allowed limit capped at 1000 MiB\u002Fs per broker, according to",[55,575,578],{"href":576,"rel":577},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fmsk\u002Flatest\u002Fdeveloperguide\u002Fmsk-provision-throughput-management.html#throughput-bottlenecks",[264]," AWS documentation",". Given this constraint, achieving 5 GB\u002Fs throughput with a replication factor of 3 required the following setup:",[339,581,582],{},[342,583,584],{},"15 × kafka.m7g.8xlarge (32 vCPUs, 128 GB memory, 15 Gbps network, 4000 GiB EBS).",[48,586,587],{},"This configuration was necessary to work around MSK's storage bandwidth limitations, ensuring a comparable cost basis to other evaluated streaming engines.",[48,589,590],{},"Additional key assumptions include:",[339,592,593,596,599],{},[342,594,595],{},"Inter-AZ producer traffic: For leader-based engines, two-thirds of producer-to-broker traffic crosses AZs due to leader distribution.",[342,597,598],{},"Consumer optimizations: Follower fetch is enabled across all tests, eliminating inter-AZ consumer traffic.",[342,600,601],{},"Storage cost exclusions: This benchmark only evaluates streaming costs, assuming no long-term data retention.",[32,603,605],{"id":604},"inter-broker-replication-costs","Inter-Broker Replication Costs",[48,607,608],{},"Inter-broker (cross-AZ) replication is a major cost driver for data streaming engines:",[339,610,611,614,617],{},[342,612,613],{},"RedPanda: Inter-broker replication is not free, leading to substantial costs when data must be copied across multiple availability zones.",[342,615,616],{},"AWS MSK: Inter-broker replication is free, but MSK instance pricing is significantly higher (e.g., $3.264 per hour for kafka.m7g.8xlarge vs $1.306 per hour for an on-demand m7g.8xlarge). The storage price of MSK is $0.10 per GB-month which is significantly higher than st1, which costs $0.045 per GB-month. Even though replication is free, client-to-broker traffic still incurs inter-AZ charges.",[342,618,619],{},"Ursa: No inter-broker replication costs due to its leaderless architecture, eliminating inter-zone replication costs entirely.",[32,621,623],{"id":622},"zone-affinity-reducing-inter-az-costs","Zone Affinity: Reducing Inter-AZ Costs",[48,625,626],{},"We evaluated zone affinity mechanisms to further reduce inter-AZ data transfer costs.",[48,628,629],{},"Consumers:",[339,631,632],{},[342,633,634],{},"Follower fetch is enabled across all tests, ensuring consumers fetch data from replicas in their local AZ—eliminating inter-zone consumer traffic except for metadata lookups",[48,636,637],{},"Producers:",[339,639,640,649,658],{},[342,641,642,643,648],{},"Kafka protocol lacks an easy way to enforce producer AZ affinity (though ",[55,644,647],{"href":645,"rel":646},"https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FKAFKA\u002FKIP-1123:+Rack-aware+partitioning+for+Kafka+Producer",[264],"KIP-1123"," aims to address this). And it only works with the default partitioner (i.e., when no record partition or record key is specified).",[342,650,651,652,657],{},"Redpanda recently introduced ",[55,653,656],{"href":654,"rel":655},"https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-cloud\u002Fdevelop\u002Fproduce-data\u002Fleader-pinning\u002F",[264],"leader pinning",", but this only benefits setups where producers are confined to a single AZ—not applicable to our multi-AZ benchmark.",[342,659,660,661,666],{},"Ursa is the only system in this test with ",[55,662,665],{"href":663,"rel":664},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fconfig-kafka-client#eliminate-cross-az-networking-traffic",[264],"built-in zone affinity for both producers and consumers",". It achieves this by embedding producer AZ information in client.id, allowing metadata lookups to route clients to local-AZ brokers, eliminating inter-AZ producer traffic.",[32,668,670],{"id":669},"cost-comparison-results","Cost Comparison Results",[48,672,337],{},[339,674,675,677],{},[342,676,344],{},[342,678,347],{},[48,680,681],{},"Ursa’s leaderless architecture, zone affinity, and native cloud storage integration deliver unparalleled cost efficiency, making it the most cost-effective choice for high-throughput data streaming workloads.",[48,683,684],{},[351,685],{"alt":18,"src":686},"\u002Fimgs\u002Fblogs\u002F679c72208198ca36a352f228_AD_4nXeeZuM8T-xBlD4Vf3j67K618n08qh8wIDLLtiLJG0ssA1Wj1V26u7wIDTX9sqLrtw8mB2c299dwzarGen62CG0Vh7nWstn5qbPGFcBaKJYEepTsLr5fHWv1U8uqbg8Y0UOK6fJ7.png",[48,688,689],{},[351,690],{"alt":18,"src":691},"\u002Fimgs\u002Fblogs\u002F679c625978031f40229de484_AD_4nXdLkLLJ30KKr-_A_rN1j8akVwBYacAWIPzWHoOReJF421890kfByZoQQxkLczihVSmiw5Q9J51-V9I2SEKITbwsYnANDDTlAVL5nQ_jfaHNTe9VEWhSoa7DZooCnilDYL6l6msmJg.png",[48,693,694],{},"The detailed infrastructure cost calculations for each data streaming engine are listed below:",[32,696,698],{"id":697},"streamnative-ursa","StreamNative - Ursa",[339,700,701,704,707,710],{},[342,702,703],{},"Server EC2 costs: 9 * $1.536\u002Fhr = $14",[342,705,706],{},"Client EC2 costs: 9 * $1.536\u002Fhr =$14",[342,708,709],{},"S3 write requests costs: 1350 r\u002Fs * $0.005\u002F1000r * 3600s = $24",[342,711,712],{},"S3 read requests costs: 1350 r\u002Fs * $0.0004\u002F1000r * 3600s = $2",[32,714,716],{"id":715},"aws-msk","AWS MSK",[339,718,719,722,725],{},[342,720,721],{},"Server EC2 costs: 15 * $3.264\u002Fhr = $49",[342,723,724],{},"Client side EC2 costs: 9 * $1.536\u002Fhr =$14",[342,726,727],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FG(in+out) * 3600 = $240",[32,729,731],{"id":730},"redpanda","RedPanda",[339,733,734,736,738,741,744],{},[342,735,703],{},[342,737,706],{},[342,739,740],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FGB(in+out) * 3600 = $240",[342,742,743],{},"Interzone traffic - replication: 10GB\u002Fs * $0.02\u002FGB(in+out) * 3600 = $720",[342,745,746],{},"Interzone traffic - broker to consumer: $0 (fetch from local zone)",[48,748,749,750,755],{},"Please note that we were unable to test ",[55,751,754],{"href":752,"rel":753},"https:\u002F\u002Fwww.redpanda.com\u002Fblog\u002Fcloud-topics-streaming-data-object-storage",[264],"Redpanda with Cloud Topics",", as it remains an announced but unreleased feature and is not yet available for evaluation. Based on the limited information available, while Cloud Topics may help optimize inter-zone data replication costs, producers still need to traverse inter-availability zones to connect to the topic partition owners and incur inter-zone traffic costs of up to $240 per hour.",[339,757,758,764],{},[342,759,760,763],{},[55,761,647],{"href":645,"rel":762},[264]," (when implemented) will help mitigate producer-to-broker inter-zone traffic, but it is not yet available. And it only works with the default partitioner (no record partition or key is specified).",[342,765,766],{},"Redpanda’s leader pinning helps only when all producers for the pinned topic are confined to a single AZ. In multi-AZ environments (like our benchmark), inter-zone producer traffic remains unavoidable.",[48,768,769],{},"Additionally, Redpanda’s Cloud Topics architecture is not documented publicly. Their blog mentions \"leader placement rules to optimize produce latency and ingress cost,\" but it is unclear whether this represents a shift away from a leader-based architecture or if it uses techniques similar to Ursa’s zone-aware approach.",[48,771,772],{},"We may revisit this comparison as more details become available.",[40,774,776],{"id":775},"comparing-total-cost-of-ownership","Comparing Total Cost of Ownership",[48,778,779],{},"As highlighted earlier, with a BYOC Ursa setup, you can achieve 5 GB\u002Fs throughput at just 5% of the infrastructure cost of a traditional leader-based data streaming engine, such as Kafka or RedPanda, while managing the infrastructure yourself. This significant cost reduction is enabled by Ursa’s leaderless architecture and lakehouse-native storage design, which eliminate overhead costs such as inter-zone traffic and leader-based data replication. By leveraging a lakehouse-native, leaderless architecture, Ursa reduces resource requirements, enabling you to handle high data throughput efficiently and at a fraction of the cost of RedPanda.",[48,781,782],{},"Now, let’s examine the total cost comparison, evaluating Ursa alongside other vendors, including those that have adopted a leaderless architecture (e.g., Confluent WarpStream). This comparison is based on a 5GB\u002Fs workload with a 7-day retention period, factoring in both storage cost and vendor costs Here are the key findings:",[339,784,785,788,791],{},[342,786,787],{},"Ursa ($164,353\u002Fmonth) is: 50% cheaper than Confluent WarpStream ($337,068\u002Fmonth)",[342,789,790],{},"85% cheaper than AWS MSK ($1,115,251\u002Fmonth)",[342,792,793],{},"86% cheaper than Redpanda ($1,202,853\u002Fmonth)",[48,795,796],{},"In addition to Ursa’s architectural advantages—eliminating most inter-AZ traffic and leveraging lakehouse storage for cost-effective data retention—it also adopts a more fair and cost-efficient pricing model: Elastic Throughput-based pricing. This approach aligns costs with actual usage, avoiding unnecessary overhead.",[48,798,799],{},"Unlike WarpStream, which charges for both storage and throughput, Ursa ensures that customers only pay for the throughput they actively use. Ursa’s pricing is based on compressed data sent by clients, meaning the more data compressed on the client side, the lower the cost. In contrast, WarpStream prices are based on uncompressed data, unfairly inflating expenses and failing to incentivize customers to optimize their client applications.",[48,801,802],{},"This distinction is crucial, as compressed data reduces both storage and network costs, making Ursa’s pricing model not only more cost-effective but also more transparent and predictable.",[48,804,805],{},[351,806],{"alt":18,"src":807},"\u002Fimgs\u002Fblogs\u002F679c602d194800c9206d9d58_AD_4nXcFlf755xgyz7htxhMhBV5fGrsxy642mQNodt61DTok_z1dwkw5A6lkO5hatXVneCaB0anbZPAyvLI3MlIMuQEYLEACHHvQMOr5UfaB37dfzkdqewDEvcT-20VGd_zzvJsuA00zGA.png",[48,809,810],{},[351,811],{"alt":18,"src":812},"\u002Fimgs\u002Fblogs\u002F679c62594e9c2e629fae73aa_AD_4nXeU6cOgItnjLsEZCOf13TEvMY_SHWWIxYP2OYUj-B1GUPyWO78OG08K_v03hwYSVcg06f9dqDiGmdwy76vynjmiDGL5bluZ5_XF4nSU_r59oOZdfViXndXt6s11vVOY7qwfZN8v.png",[32,814,816],{"id":815},"cost-breakdown","Cost Breakdown",[818,819,820],"h4",{"id":697},"StreamNative – Ursa",[339,822,823,826,829,832,835],{},[342,824,825],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9,953.28",[342,827,828],{},"S3 Write Requests: 1,350 r\u002Fs × $0.005\u002F1,000 r × 3,600 s × 24 hr × 30 days = $17,496",[342,830,831],{},"S3 Read Requests: 1,350 r\u002Fs × $0.0004\u002F1,000 r × 3,600 s × 24 hr × 30 days = $1,400",[342,833,834],{},"S3 Storage Costs: 5 GB\u002Fs × $0.021\u002FGB × 3,600 s × 24 hr × 7 days = $63,504",[342,836,837],{},"Vendor Cost: 200 ETU × $0.50\u002Fhr × 24 hr × 30 days = $72,000",[818,839,841],{"id":840},"warpstream","WarpStream",[339,843,844,847],{},[342,845,846],{},"Based on WarpStream’s pricing calculator (as of January 29, 2025), we assume a 4:1 client data compression ratio, meaning 20 GB\u002Fs of uncompressed data translates to 5 GB\u002Fs of compressed data.",[342,848,849,850,855],{},"It's important to note that WarpStream’s pricing structure has fluctuated frequently throughout January. We observed the cost reported by their calculator changing from $409,644 per month to $337,068 per month. This variability has been previously highlighted in the blog post “",[55,851,854],{"href":852,"rel":853},"https:\u002F\u002Fbigdata.2minutestreaming.com\u002Fp\u002Fthe-brutal-truth-about-apache-kafka-cost-calculators",[264],"The Brutal Truth About Kafka Cost Calculators","”. To ensure transparency, we have documented the pricing as of January 29, 2025.",[48,857,858],{},[351,859],{"alt":18,"src":860},"\u002Fimgs\u002Fblogs\u002F679c602e42713e0028e9af5e_AD_4nXcu5_VWTLu9jRYs6zX1MBAOtLQEo5gyfNSWPcbpnQHXTa8qNCFAXezRR2E8daygzYTTwd4dhJjaLaLM8C6y_3OGbu2NS7pdvEv3a8-ptNKOg7AeKnYqPQCAYvQ5EuxzuI3JYIvY.png",[818,862,864],{"id":863},"msk","MSK",[339,866,867,870,873],{},[342,868,869],{},"EC2 (Server): 15 * $3.264\u002Fhr × 24 hr × 30 days = $35,251",[342,871,872],{},"Interzone Traffic (Client-Server): 5 GB\u002Fs × ⅔ × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $172,800",[342,874,875],{},"Storage: 5 GB\u002Fs × $0.1\u002FGB-month × 3,600 s × 24 hr × 7 days * 3 replicas = $907,200",[818,877,731],{"id":878},"redpanda-1",[339,880,881,884,886,889,892],{},[342,882,883],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9953",[342,885,872],{},[342,887,888],{},"Interzone Traffic (Replication): 5 GB\u002Fs × 2 × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $518,400",[342,890,891],{},"Storage: 5 GB\u002Fs × $0.045\u002FGB-month(st1) × 3,600 s × 24 hr × 7 days * 3 replicas = $408,240",[342,893,894],{},"Vendor Cost: $93,333 per month (based on limited information. See additional notes below).",[818,896,898],{"id":897},"additional-notes","Additional Notes",[339,900,901],{},[342,902,903,904,909],{},"Redpanda does not publicly disclose its BYOC pricing, making it difficult to accurately assess its total costs. We refer to information from the whitepaper “",[55,905,908],{"href":906,"rel":907},"https:\u002F\u002Fwww.redpanda.com\u002Fresources\u002Fredpanda-vs-confluent-performance-tco-benchmark-report#form",[264],"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group.","” for estimation purposes. Based on the Tier-8 pricing model in the whitepaper,  the estimated cost to support a 5GB\u002Fs workload would be $1.12 million per year ($93,333 per month). However, since this calculation is based on an estimation, we will revisit and refine the cost assessment once Redpanda publishes its BYOC pricing.",[48,911,912],{},[351,913],{"alt":18,"src":914},"\u002Fimgs\u002Fblogs\u002F679c602dc8a9859eed89a0ef_AD_4nXdbcO8vsNNPy4GtkNLlmNKf22fjxRvzLzH7CtOna1L08sTbvnZx3HhufeFqc1w4K2gEF7lxO2IR5supotxebAiGnA07Qa8Yr3Rd1pVK2LYKK4WurlJGwgdwwucZIFoF-N_2oBjY.png",[48,916,917],{},[351,918],{"alt":18,"src":919},"\u002Fimgs\u002Fblogs\u002F679c602d6bc1c2287e012540_AD_4nXfcHZnLfjbjIr3ZAgoQXT9dwP3aQCOQPmGZZJUtpNZSwE6qY6M3yehIaBxCwxEIeu5PVdUPY0zhyjnow26YfgjdYgSG4GnV9ibxu0YWTIpwng6z_F6FUGJMpERMKtpsFESzXSN_Sw.png",[339,921,922,925],{},[342,923,924],{},"When estimating the storage costs for Kafka and Redpanda, we assume the use of HDD storage at $0.045\u002FGB, based on the premise that both systems can fully utilize disk bandwidth without incurring the higher costs associated with GP2 or GP3 volumes. However, in practice, many users opt for GP2 or GP3, significantly increasing the total storage cost for Kafka and Redpanda.",[342,926,927],{},"Unlike disk-based solutions, S3 storage does not require capacity preallocation—Ursa only incurs costs for the actual data stored. This contrasts with Kafka and Redpanda, where preallocating storage can drive up expenses. As a result, the real-world storage costs for Kafka and Redpanda are often 50% higher than the estimates above.",[40,929,931],{"id":930},"conclusion","Conclusion",[48,933,934],{},"Ursa represents a transformative shift in streaming data infrastructure, offering cost efficiency, scalability, and flexibility without compromising durability or reliability. By leveraging a leaderless architecture and eliminating inter-zone data replication, Ursa reduces total cost of ownership by over 90% compared to traditional leader-based streaming engines like Kafka and Redpanda. Its direct integration with cloud storage and scalable metadata & index management via Oxia ensure high availability and simplified infrastructure management.",[32,936,938],{"id":937},"balancing-latency-and-cost","Balancing Latency and Cost",[48,940,941,945],{},[55,942,944],{"href":943},"\u002Fblog\u002Fcap-theorem-for-data-streaming","Ursa trades off slightly higher latency for ultra low cost",", making it an ideal choice for the majority of streaming workloads, especially those that prioritize throughput and cost savings over ultra-low latency. Meanwhile, StreamNative’s BookKeeper-based engine remains the preferred solution for real-time, latency-sensitive applications. By combining these two approaches, StreamNative empowers customers with the flexibility to choose the right engine for their specific needs—whether it's maximizing cost savings or achieving ultra low-latency real-time performance.",[32,947,949],{"id":948},"the-future-of-streaming-infrastructure","The Future of Streaming Infrastructure",[48,951,952],{},"In an era where data fuels AI, analytics, and real-time decision-making, managing infrastructure costs is critical to sustaining innovation. Ursa is not just a cost-cutting alternative—it is a forward-thinking, lakehouse-native platform that redefines how modern data streaming infrastructure should be built and operated.",[48,954,955,956,961],{},"Whether your priority is reducing costs, improving flexibility, or ingesting massive data into lakehouses, Ursa delivers a future-proof solution for the evolving demands of real-time data streaming. ",[55,957,960],{"href":958,"rel":959},"https:\u002F\u002Fconsole.streamnative.cloud\u002F",[264],"Get started"," with StreamNative Ursa today!",[963,964,966],"h1",{"id":965},"references","References",[48,968,969,972,973],{},[970,971,430],"span",{}," ",[55,974,975],{"href":975},"\u002Fblog\u002Fintroducing-oxia-scalable-metadata-and-coordination",[48,977,978,972,980],{},[970,979,379],{},[55,981,378],{"href":378},[48,983,984,972,987],{},[970,985,986],{},"StreamNative pricing",[55,988,989],{"href":989,"rel":990},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fbilling-overview",[264],[48,992,993,972,996],{},[970,994,995],{},"WarpStream pricing",[55,997,998],{"href":998,"rel":999},"https:\u002F\u002Fwww.warpstream.com\u002Fpricing#pricingfaqs",[264],[48,1001,1002,972,1005],{},[970,1003,1004],{},"AWS S3 pricing",[55,1006,1007],{"href":1007,"rel":1008},"https:\u002F\u002Faws.amazon.com\u002Fs3\u002Fpricing\u002F",[264],[48,1010,1011,972,1014],{},[970,1012,1013],{},"AWS EBS pricing",[55,1015,1016],{"href":1016,"rel":1017},"https:\u002F\u002Faws.amazon.com\u002Febs\u002Fpricing\u002F",[264],[48,1019,1020,972,1023],{},[970,1021,1022],{},"AWS MSK pricing",[55,1024,1025],{"href":1025,"rel":1026},"https:\u002F\u002Faws.amazon.com\u002Fmsk\u002Fpricing\u002F",[264],[48,1028,1029,972,1032],{},[970,1030,1031],{},"The Brutal Truth about Kafka Cost Calculators",[55,1033,852],{"href":852,"rel":1034},[264],[48,1036,1037,972,1040],{},[970,1038,1039],{},"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group",[55,1041,906],{"href":906,"rel":1042},[264],{"title":18,"searchDepth":19,"depth":19,"links":1044},[1045,1046,1047,1052,1056,1057,1066,1069],{"id":333,"depth":19,"text":334},{"id":372,"depth":19,"text":373},{"id":397,"depth":19,"text":398,"children":1048},[1049,1050,1051],{"id":409,"depth":279,"text":410},{"id":434,"depth":279,"text":435},{"id":455,"depth":279,"text":456},{"id":479,"depth":19,"text":480,"children":1053},[1054,1055],{"id":483,"depth":279,"text":484},{"id":498,"depth":279,"text":499},{"id":539,"depth":19,"text":540},{"id":551,"depth":19,"text":552,"children":1058},[1059,1060,1061,1062,1063,1064,1065],{"id":558,"depth":279,"text":559},{"id":604,"depth":279,"text":605},{"id":622,"depth":279,"text":623},{"id":669,"depth":279,"text":670},{"id":697,"depth":279,"text":698},{"id":715,"depth":279,"text":716},{"id":730,"depth":279,"text":731},{"id":775,"depth":19,"text":776,"children":1067},[1068],{"id":815,"depth":279,"text":816},{"id":930,"depth":19,"text":931,"children":1070},[1071,1072],{"id":937,"depth":279,"text":938},{"id":948,"depth":279,"text":949},"StreamNative Cloud","2025-01-31","Discover how Ursa achieves 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda and AWS MSK. See our benchmark results comparing infrastructure costs, total cost of ownership (TCO), and performance across leading Kafka vendors.","\u002Fimgs\u002Fblogs\u002F679c6593d25099b1cdcec4ca_image-31.png",{},"\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour","30 min",{"title":308,"description":1075},"blog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour",[1083,1084,303],"TCO","Apache Kafka","A0o_2xdJiLI6rf6xj4RKsxJNo_A6QN2fYzCp6gaLrFw",{"id":1087,"title":1088,"authors":1089,"body":1090,"category":2118,"createdAt":290,"date":2119,"description":2120,"extension":8,"featured":294,"image":2121,"isDraft":294,"link":290,"meta":2122,"navigation":7,"order":296,"path":2123,"readingTime":2124,"relatedResources":290,"seo":2125,"stem":2126,"tags":2127,"__hash__":2128},"blogs\u002Fblog\u002Fapache-pulsar-2-6-0.md","Apache Pulsar 2.6.0",[313],{"type":15,"value":1091,"toc":2052},[1092,1095,1098,1102,1109,1112,1122,1139,1146,1149,1152,1168,1175,1183,1199,1206,1209,1215,1231,1238,1241,1244,1250,1266,1273,1276,1279,1295,1302,1305,1311,1314,1320,1336,1343,1346,1362,1369,1372,1378,1381,1387,1396,1403,1406,1409,1415,1418,1427,1433,1436,1439,1442,1448,1463,1469,1472,1475,1481,1490,1494,1497,1506,1515,1519,1522,1525,1531,1540,1544,1547,1550,1556,1565,1569,1578,1587,1591,1594,1597,1603,1612,1616,1619,1622,1625,1631,1640,1644,1647,1653,1662,1666,1669,1675,1684,1691,1700,1704,1707,1710,1719,1723,1727,1730,1733,1742,1746,1750,1753,1762,1766,1769,1778,1782,1786,1789,1798,1802,1811,1815,1818,1827,1831,1840,1844,1847,1856,1860,1864,1867,1870,1879,1883,1886,1895,1899,1903,1906,1909,1918,1922,1925,1928,1937,1941,1944,1947,1956,1960,1964,1986,1989,2009,2016,2024,2028,2041,2049],[48,1093,1094],{},"We are very glad to see the Apache Pulsar community has successfully released the wonderful 2.6.0 version after accumulated hard work. It is a great milestone for this fast-growing project and the whole Pulsar community. This is the result of a huge effort from the community, with over 450 commits and a long list of new features, improvements, and bug fixes.",[48,1096,1097],{},"Here is a selection of some of the most interesting and major features added to Pulsar 2.6.0.",[40,1099,1101],{"id":1100},"core-pulsar","Core Pulsar",[32,1103,1105,1108],{"id":1104},"pip-37-large-message-size-support",[970,1106,1107],{},"PIP-37"," Large message size support",[48,1110,1111],{},"This PIP adds support for producing and consuming large size messages by splitting the large message into multiple chunks. This is a very powerful feature for sending and consuming very large messages. Currently, this feature only works for the non-shared subscription and it has client-side changes. You need to upgrade the Pulsar client version to 2.6.0. You can enable the message trunk at the producer side as below.",[1113,1114,1119],"pre",{"className":1115,"code":1117,"language":1118},[1116],"language-text","\nclient.newProducer()\n    .topic(\"my-topic\")\n    .enableChunking(true)\n    .create();\n\n","text",[1120,1121,1117],"code",{"__ignoreMap":18},[339,1123,1124,1131],{},[342,1125,1126,1127,190],{},"For more information about PIP-37, see ",[55,1128,267],{"href":1129,"rel":1130},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-37:-Large-message-size-handling-in-Pulsar",[264],[342,1132,1133,1134,190],{},"For more information about implementation details, see ",[55,1135,1138],{"href":1136,"rel":1137},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F4400",[264],"PR-4440",[32,1140,1142,1145],{"id":1141},"pip-39-namespace-change-events-system-topic",[970,1143,1144],{},"PIP-39"," Namespace change events (system topic)",[48,1147,1148],{},"This PIP introduces the system topic to store namespace change events.",[48,1150,1151],{},"Previously, Pulsar only allowed you to set the namespace policy, all topics under the namespace followed the namespace policy. Many users want to set the policy for topics. The main reason for not using the same way as namespace level policy is to avoid introducing more workload on ZooKeeper. The original intention of the system topic is to be able to store topic policy in a topic rather than ZooKeeper. So this is the first step to achieve topic level policy. And we can easily add support for the topic level policy with this feature.",[339,1153,1154,1161],{},[342,1155,1156,1157,190],{},"For more information about PIP-39, see ",[55,1158,267],{"href":1159,"rel":1160},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-39%3A-Namespace-Change-Events",[264],[342,1162,1133,1163,190],{},[55,1164,1167],{"href":1165,"rel":1166},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F4955",[264],"PR-4955",[32,1169,1171,1174],{"id":1170},"pip-45-pluggable-metadata-interface",[970,1172,1173],{},"PIP-45"," Pluggable metadata interface",[48,1176,1177,1178,190],{},"We have been advancing to enable Pulsar to use other metastore services rather than ZooKeeper. This PIP converts ManagedLedger to use the MetadataStore interface. This facilitates the metadata server plug-in process. Through the MetadataStore interface, it is easy to add other metadata servers into Pulsar such as ",[55,1179,1182],{"href":1180,"rel":1181},"https:\u002F\u002Fgithub.com\u002Fetcd-io\u002Fetcd",[264],"etcd",[339,1184,1185,1192],{},[342,1186,1187,1188,190],{},"For more information about PIP-45, see ",[55,1189,267],{"href":1190,"rel":1191},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-45%3A-Pluggable-metadata-interface",[264],[342,1193,1133,1194,190],{},[55,1195,1198],{"href":1196,"rel":1197},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F5358",[264],"PR-5358",[32,1200,1202,1205],{"id":1201},"pip-54-support-acknowledgment-at-the-batch-index-level",[970,1203,1204],{},"PIP-54"," Support acknowledgment at the batch index level",[48,1207,1208],{},"Previously, the broker only tracked the acknowledged state in the batch message level. If a subset of the batch messages was acknowledged, the consumer could still get the acknowledged message of that batch message while the batch message redelivery happened. This PIP adds support for acknowledging the local batch index of a batch. This feature is not enabled by default. You can enable it in the broker.conf as below.",[1113,1210,1213],{"className":1211,"code":1212,"language":1118},[1116],"\nbatchIndexAcknowledgeEnable=true\n\n",[1120,1214,1212],{"__ignoreMap":18},[339,1216,1217,1224],{},[342,1218,1219,1220,190],{},"For more information about PIP-54, see ",[55,1221,267],{"href":1222,"rel":1223},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-54:-Support-acknowledgment-at-batch-index-level",[264],[342,1225,1133,1226,190],{},[55,1227,1230],{"href":1228,"rel":1229},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6052",[264],"PR-6052",[32,1232,1234,1237],{"id":1233},"pip-58-support-consumers-setting-custom-message-retry-delay",[970,1235,1236],{},"PIP-58"," Support consumers setting custom message retry delay",[48,1239,1240],{},"For many online business systems, various exceptions usually occur in business logic processing, so the message needs to be re-consumed, but users hope that this delay time can be controlled flexibly. Previously, processing methods were usually to send messages to special retry topics, because production can specify any delay, so consumers subscribe to the business topic and retry topic at the same time.",[48,1242,1243],{},"Previously, Pulsar redelivered messages immediately when clients sent negative acknowledgments to brokers. Now you can set a retry delay for each message as below.",[1113,1245,1248],{"className":1246,"code":1247,"language":1118},[1116],"\nConsumer consumer = pulsarClient.newConsumer(Schema.BYTES)\n                .enableRetry(true)\n                .receiverQueueSize(100)\n                .deadLetterPolicy(DeadLetterPolicy.builder()\n                    .maxRedeliverCount(maxRedeliveryCount)\n                   .retryLetterTopic(\"persistent:\u002F\u002Fmy-property\u002Fmy-ns\u002Fmy-subscription-custom-Retry\")\n                        .build())\n                .subscribe();\n\nconsumer.reconsumeLater(message, 10 , TimeUnit.SECONDS);\n \n",[1120,1249,1247],{"__ignoreMap":18},[339,1251,1252,1259],{},[342,1253,1254,1255,190],{},"For more information about PIP-58, see ",[55,1256,267],{"href":1257,"rel":1258},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-58-%3A-Support-Consumers--Set-Custom-Retry-Delay",[264],[342,1260,1133,1261,190],{},[55,1262,1265],{"href":1263,"rel":1264},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6449",[264],"PR-6449",[32,1267,1269,1272],{"id":1268},"pip-60-support-sni-routing-to-support-various-proxy-servers",[970,1270,1271],{},"PIP-60"," Support SNI routing to support various proxy servers",[48,1274,1275],{},"Previously, Pulsar did not provide support to use other proxies, such as Apache Traffic Server (ATS), HAProxy, Nginx, and Envoy, which are more scalable and secured. Most of these proxy servers support SNI routing which can route traffic to a destination without having to terminate the SSL connection.",[48,1277,1278],{},"This PIP adds SNI routing and makes changes to the Pulsar client.",[339,1280,1281,1288],{},[342,1282,1283,1284,190],{},"For more information about PIP-60, see ",[55,1285,267],{"href":1286,"rel":1287},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-60:-Support-Proxy-server-with-SNI-routing",[264],[342,1289,1133,1290,190],{},[55,1291,1294],{"href":1292,"rel":1293},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6566",[264],"PR-6566",[32,1296,1298,1301],{"id":1297},"pip-61-advertise-multiple-addresses",[970,1299,1300],{},"PIP-61"," Advertise multiple addresses",[48,1303,1304],{},"This PIP allows the broker to expose multiple advertised listeners and to support the separation of internal and external network traffic. You can specify multiple advertised listeners in broker.conf as below.",[1113,1306,1309],{"className":1307,"code":1308,"language":1118},[1116],"\nadvertisedListeners=internal:pulsar:\u002F\u002F192.168.1.11:6660,external:pulsar:\u002F\u002F110.95.234.50:6650\n\n",[1120,1310,1308],{"__ignoreMap":18},[48,1312,1313],{},"From the client side, you can specify the listener name for the client as below.",[1113,1315,1318],{"className":1316,"code":1317,"language":1118},[1116],"\nPulsarClient.builder()\n.serviceUrl(url)\n.listenerName(\"internal\")\n.build();\n\n",[1120,1319,1317],{"__ignoreMap":18},[339,1321,1322,1329],{},[342,1323,1324,1325,190],{},"For more information about PIP-61, see ",[55,1326,267],{"href":1327,"rel":1328},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-61%3A-Advertised-multiple-addresses",[264],[342,1330,1133,1331,190],{},[55,1332,1335],{"href":1333,"rel":1334},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6903",[264],"PR-6903",[32,1337,1339,1342],{"id":1338},"pip-65-adapt-pulsar-io-sources-to-support-batchsources",[970,1340,1341],{},"PIP-65"," Adapt Pulsar IO sources to support BatchSources",[48,1344,1345],{},"This PIP introduces BatchSource as a new interface for writing batch-based connectors. It also introduces BatchSourceTriggerer as an interface to trigger the data collection of a BatchSource. It then provides system implementation in BatchSourceExecutor.",[339,1347,1348,1355],{},[342,1349,1350,1351,190],{},"For more information about PIP-65, see ",[55,1352,267],{"href":1353,"rel":1354},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fwiki\u002FPIP-65%3A-Adapting-Pulsar-IO-Sources-to-support-Batch-Sources",[264],[342,1356,1133,1357,190],{},[55,1358,1361],{"href":1359,"rel":1360},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7090",[264],"PR-7090",[32,1363,1365,1368],{"id":1364},"load-balancer-add-thresholdshedder-strategy-for-the-load-balancer",[970,1366,1367],{},"Load balancer"," Add ThresholdShedder strategy for the load balancer",[48,1370,1371],{},"The ThresholdShedder strategy is more flexible than LoadSheddingStrategy for Pulsar. The ThresholdShedder calculates the average resource usage of the brokers, and individual broker resource usage compares with the average value. If it is greater than the average value plus threshold, the overload shedder is triggered. You can enable it in broker.conf as below.",[1113,1373,1376],{"className":1374,"code":1375,"language":1118},[1116],"\nloadBalancerLoadSheddingStrategy=org.apache.pulsar.broker.loadbalance.impl.ThresholdShedder\n\n",[1120,1377,1375],{"__ignoreMap":18},[48,1379,1380],{},"You can customize more parameters for the ThresholdShedder if needed as below.",[1113,1382,1385],{"className":1383,"code":1384,"language":1118},[1116],"\n# The broker resource usage threshold.\n# When the broker resource usage is greater than the pulsar cluster average resource usage,\n# the threshold shedder will be triggered to offload bundles from the broker.\n# It only takes effect in ThresholdSheddler strategy.\nloadBalancerBrokerThresholdShedderPercentage=10\n\n# When calculating new resource usage, the history usage accounts for.\n# It only takes effect in ThresholdSheddler strategy.\nloadBalancerHistoryResourcePercentage=0.9\n\n# The BandWithIn usage weight when calculating new resource usage.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerBandwidthInResourceWeight=1.0\n\n# The BandWithOut usage weight when calculating new resource usage.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerBandwidthOutResourceWeight=1.0\n\n# The CPU usage weight when calculating new resource usage.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerCPUResourceWeight=1.0\n\n# The heap memory usage weight when calculating new resource usage.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerMemoryResourceWeight=1.0\n\n# The direct memory usage weight when calculating new resource usage.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerDirectMemoryResourceWeight=1.0\n\n# Bundle unload minimum throughput threshold (MB), avoiding bundle unload frequently.\n# It only takes effect in ThresholdShedder strategy.\nloadBalancerBundleUnloadMinThroughputThreshold=10\n\n",[1120,1386,1384],{"__ignoreMap":18},[339,1388,1389],{},[342,1390,1133,1391,190],{},[55,1392,1395],{"href":1393,"rel":1394},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6772",[264],"PR-6772",[32,1397,1399,1402],{"id":1398},"key-shared-add-consistent-hashing-in-the-key_shared-distribution",[970,1400,1401],{},"Key Shared"," Add consistent hashing in the Key_Shared distribution",[48,1404,1405],{},"Previously, the implementation of the Key_Shared subscription used a mechanism to divide their hash space across the available consumers. This was based on dividing the currently assigned hash ranges when a new consumer joined or left.",[48,1407,1408],{},"Pulsar 2.6.0 introduces a new consistent hash distribution for the Key_Shared subscription. You can enable the consistent hash distribution in broker.conf and the auto split approach is still selected by default.",[1113,1410,1413],{"className":1411,"code":1412,"language":1118},[1116],"\n# On KeyShared subscriptions, with default AUTO_SPLIT mode, use splitting ranges or\n# consistent hashing to reassign keys to new consumers\nsubscriptionKeySharedUseConsistentHashing=false\n\n# On KeyShared subscriptions, number of points in the consistent-hashing ring.\n# The higher the number, the more equal the assignment of keys to consumers\nsubscriptionKeySharedConsistentHashingReplicaPoints=100\n\n",[1120,1414,1412],{"__ignoreMap":18},[48,1416,1417],{},"We plan to use consistent hash distribution by default in the subsequent versions.",[339,1419,1420],{},[342,1421,1133,1422,190],{},[55,1423,1426],{"href":1424,"rel":1425},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6791",[264],"PR-6791",[32,1428,1430,1432],{"id":1429},"key-shared-fix-ordering-issue-in-keyshared-dispatcher-when-adding-consumers",[970,1431,1401],{}," Fix ordering issue in KeyShared dispatcher when adding consumers",[48,1434,1435],{},"This is a great fix for the Key_Shared subscription. Previously, ordering was broken in a KeyShared dispatcher if a new consumer c2 came in and an existing consumer c1 went out. This was because messages with keys previously assigned to c1 may route to c2, which might break the message ordering dispatch guarantee in the Key_Shared subscription.",[48,1437,1438],{},"This PR introduces new consumers joining in a \"paused\" state until the previous messages are acknowledged to ensure the messages are dispatched orderly.",[48,1440,1441],{},"If you still want the relaxed ordering, you can set up at the consumer side as below.",[1113,1443,1446],{"className":1444,"code":1445,"language":1118},[1116],"\npulsarClient.newConsumer()\n    .keySharedPolicy(KeySharedPolicy.autoSplitHashRange().setAllowOutOfOrderDelivery(true))\n    .subscribe();\n\n",[1120,1447,1445],{"__ignoreMap":18},[339,1449,1450],{},[342,1451,1133,1452,1457,1458,190],{},[55,1453,1456],{"href":1454,"rel":1455},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7106",[264],"PR-7106"," and ",[55,1459,1462],{"href":1460,"rel":1461},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7108",[264],"PR-7108",[32,1464,1466,1468],{"id":1465},"key-shared-add-support-for-key-hash-range-reading",[970,1467,1401],{}," Add support for key hash range reading",[48,1470,1471],{},"This PR supports sticky key hash range reader. A broker only dispatches messages whose hash of the message key contains by a specified key hash range.",[48,1473,1474],{},"Besides, multiple key hash ranges can be specified on a reader.",[1113,1476,1479],{"className":1477,"code":1478,"language":1118},[1116],"\npulsarClient.newReader()\n                    .topic(topic)\n                    .startMessageId(MessageId.earliest)\n                    .keyHashRange(Range.of(0, 10000), Range.of(20001, 30000))\n                    .create();\n\n",[1120,1480,1478],{"__ignoreMap":18},[339,1482,1483],{},[342,1484,1133,1485,190],{},[55,1486,1489],{"href":1487,"rel":1488},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F5928",[264],"PR-5928",[32,1491,1493],{"id":1492},"use-pure-java-air-compressor-instead-of-jni-based-libraries","Use pure-java Air-Compressor instead of JNI based libraries",[48,1495,1496],{},"Previously, JNI based libraries were used to perform data compression. While these libraries do have an overhead in terms of size and affect the JNI overhead which is typically measurable when compressing many small payloads.",[48,1498,1499,1500,1505],{},"This PR replaces compression libraries for LZ4, ZStd, and Snappy with ",[55,1501,1504],{"href":1502,"rel":1503},"https:\u002F\u002Fgithub.com\u002Fairlift\u002Faircompressor",[264],"AirCompressor",", which is a pure Java compression library used by Presto.",[339,1507,1508],{},[342,1509,1133,1510,190],{},[55,1511,1514],{"href":1512,"rel":1513},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F5390",[264],"PR-5390",[32,1516,1518],{"id":1517},"support-multiple-pulsar-clusters-using-the-same-bookkeeper-cluster","Support multiple Pulsar clusters using the same BookKeeper cluster",[48,1520,1521],{},"This PR allows multiple Pulsar clusters to use the specified BookKeeper cluster by pointing BookKeeper client to the ZooKeeper connection string of BookKeeper cluster.",[48,1523,1524],{},"This PR adds a configuration (bookkeeperMetadataServiceUri) to discover BookKeeper cluster metadata store and uses metadata service URI to initialize BookKeeper clients.",[1113,1526,1529],{"className":1527,"code":1528,"language":1118},[1116],"\n# Metadata service uri that bookkeeper is used for loading corresponding metadata driver\n# and resolving its metadata service location.\n# This value can be fetched using `bookkeeper shell whatisinstanceid` command in BookKeeper cluster.\n# For example: zk+hierarchical:\u002F\u002Flocalhost:2181\u002Fledgers\n# The metadata service uri list can also be semicolon separated values like below:\n# zk+hierarchical:\u002F\u002Fzk1:2181;zk2:2181;zk3:2181\u002Fledgers\nbookkeeperMetadataServiceUri=\n\n",[1120,1530,1528],{"__ignoreMap":18},[339,1532,1533],{},[342,1534,1133,1535,190],{},[55,1536,1539],{"href":1537,"rel":1538},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F5985",[264],"PR-5985",[32,1541,1543],{"id":1542},"support-deleting-inactive-topics-when-subscriptions-are-caught-up","Support deleting inactive topics when subscriptions are caught up",[48,1545,1546],{},"Previously, Pulsar supported deleting inactive topics which do not have active producers and subscriptions. This PR supports deleting inactive topics when all subscriptions of the topic are caught up and when there are no active producers or consumers.",[48,1548,1549],{},"This PR exposes inactive topic delete mode in broker.conf. In the future, we can support a namespace level configuration for the inactive topic delete mode.",[1113,1551,1554],{"className":1552,"code":1553,"language":1118},[1116],"\n# Set the inactive topic delete mode. Default is delete_when_no_subscriptions\n# 'delete_when_no_subscriptions' mode only delete the topic which has no subscriptions and no active producers\n# 'delete_when_subscriptions_caught_up' mode only delete the topic that all subscriptions has no backlogs(caught up)\n# and no active producers\u002Fconsumers\nbrokerDeleteInactiveTopicsMode=delete_when_no_subscriptions\n\n",[1120,1555,1553],{"__ignoreMap":18},[339,1557,1558],{},[342,1559,1133,1560,190],{},[55,1561,1564],{"href":1562,"rel":1563},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6077",[264],"PR-6077",[32,1566,1568],{"id":1567},"add-a-flag-to-skip-broker-shutdown-on-transient-oom","Add a flag to skip broker shutdown on transient OOM",[48,1570,1571,1572,1577],{},"A high dispatch rate on one of the topics may cause a broker to go OOM temporarily. It is a transient error and the broker can recover within a few seconds as soon as some memory gets released. However, in 2.4 release (",[55,1573,1576],{"href":1574,"rel":1575},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F4196",[264],"#4196","), the “restarted broker on OOM” feature can cause huge instability in a cluster, where a topic moves from one broker to another and restarts multiple brokers and disrupt other topics as well. So this PR provides a dynamic flag to skip broker shutdown on OOM to avoid instability in a cluster.",[339,1579,1580],{},[342,1581,1133,1582,190],{},[55,1583,1586],{"href":1584,"rel":1585},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6634",[264],"PR-6634",[32,1588,1590],{"id":1589},"make-zookeeper-cache-expiry-time-configurable","Make ZooKeeper cache expiry time configurable",[48,1592,1593],{},"Previously, ZooKeeper cache expiry time was hardcoded and it needed to be configurable to refresh value based on various requirements, for example, refreshing value quickly in case of zk-watch miss, avoiding frequent cache refresh to avoid zk-read or avoiding issue due to zk read timeout, and so on.",[48,1595,1596],{},"Now you can configure ZooKeeper cache expiry time in broker.conf as below.",[1113,1598,1601],{"className":1599,"code":1600,"language":1118},[1116],"\n# ZooKeeper cache expiry time in seconds\nzooKeeperCacheExpirySeconds=300\n\n",[1120,1602,1600],{"__ignoreMap":18},[339,1604,1605],{},[342,1606,1133,1607,190],{},[55,1608,1611],{"href":1609,"rel":1610},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6668",[264],"PR-6668",[32,1613,1615],{"id":1614},"optimize-consumer-fetch-messages-in-case-of-batch-message","Optimize consumer fetch messages in case of batch message",[48,1617,1618],{},"When a consumer sends a fetch request to a broker server, it contains a fetch message number telling the server how many messages should be pushed to a consumer client. However, the broker server stores data in BookKeeper or broker cache according to entry rather than a single message if the producer produces messages using the batch feature. There is a gap to map the number of messages to the number of entries when dealing with consumer fetch requests.",[48,1620,1621],{},"This PR adds a variable avgMessagesPerEntry to record average messages stored in one entry. It updates when a broker server pushes messages to a consumer. When dealing with consumer fetch requests, it maps fetch request number to entry number. Additionally, this PR exposes the avgMessagePerEntry static value to consumer stat metric json.",[48,1623,1624],{},"You can enable preciseDispatcherFlowControl in broker.conf as below.",[1113,1626,1629],{"className":1627,"code":1628,"language":1118},[1116],"\n# Precise dispatcher flow control according to history message number of each entry\npreciseDispatcherFlowControl=false\n\n",[1120,1630,1628],{"__ignoreMap":18},[339,1632,1633],{},[342,1634,1133,1635,190],{},[55,1636,1639],{"href":1637,"rel":1638},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6719",[264],"PR-6719",[32,1641,1643],{"id":1642},"introduce-precise-topic-publish-rate-limiting","Introduce precise topic publish rate limiting",[48,1645,1646],{},"Previously, Pulsar supported the publish rate limiting but it is not a precise control. Now, for some use cases that need precise control, you can enable it in broker.conf as below.",[1113,1648,1651],{"className":1649,"code":1650,"language":1118},[1116],"\npreciseTopicPublishRateLimiterEnable=true\n\n",[1120,1652,1650],{"__ignoreMap":18},[339,1654,1655],{},[342,1656,1133,1657,190],{},[55,1658,1661],{"href":1659,"rel":1660},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7078",[264],"PR-7078",[32,1663,1665],{"id":1664},"expose-check-delay-of-new-entries-in-brokerconf","Expose check delay of new entries in broker.conf",[48,1667,1668],{},"Previously, the check delay of new entries was 10 ms and could not be changed by users. Currently, for consumption latency sensitive scenarios, you can set the value of check delay of new entries to a smaller value or 0 in broker.conf as below. Using a smaller value may degrade consumption throughput.",[1113,1670,1673],{"className":1671,"code":1672,"language":1118},[1116],"\nmanagedLedgerNewEntriesCheckDelayInMillis=10\n\n",[1120,1674,1672],{"__ignoreMap":18},[339,1676,1677],{},[342,1678,1133,1679,190],{},[55,1680,1683],{"href":1681,"rel":1682},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7154",[264],"PR-7154",[32,1685,1687,1690],{"id":1686},"schema-support-null-key-and-null-value-in-keyvalue-schema",[970,1688,1689],{},"Schema"," Support null key and null value in KeyValue schema",[339,1692,1693],{},[342,1694,1133,1695,190],{},[55,1696,1699],{"href":1697,"rel":1698},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7139",[264],"PR-7139",[32,1701,1703],{"id":1702},"support-triggering-ledger-rollover-when-maxledgerrollovertimeminutes-is-met","Support triggering ledger rollover when maxLedgerRolloverTimeMinutes is met",[48,1705,1706],{},"This PR implements a monitoring thread to check if the current topic ledger meets the constraint of managedLedgerMaxLedgerRolloverTimeMinutes and triggers a rollover to make the configuration take effect. Another important idea is that if you trigger a rollover, you can close the current ledger so that you can release the storage of the current ledger. For some less commonly used topics, the current ledger data is likely to be expired and the current rollover logic is only triggered when adding a new entry. Obviously, this results in a waste of disk space.",[48,1708,1709],{},"The monitoring thread is scheduled at a fixed time interval and the interval is set to managedLedgerMaxLedgerRolloverTimeMinutes. Each inspection makes two judgments at the same time, for example, currentLedgerEntries > 0 and currentLedgerIsFull(). When the number of current entries is equal to 0, it does not trigger a new rollover and you can use this to reduce the ledger creation.",[339,1711,1712],{},[342,1713,1133,1714,190],{},[55,1715,1718],{"href":1716,"rel":1717},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F7111",[264],"PR-7116",[40,1720,1722],{"id":1721},"proxy","Proxy",[32,1724,1726],{"id":1725},"add-rest-api-to-get-connection-and-topic-stats","Add REST API to get connection and topic stats",[48,1728,1729],{},"Previously, Pulsar proxy did not have useful stats to get internal information about the proxy. It is better to have internal-stats of proxy to get information, such as live connections, topic stats (with higher logging level), and so on.",[48,1731,1732],{},"This PR adds REST API to get stats for connection and topics served by proxy.",[339,1734,1735],{},[342,1736,1133,1737,190],{},[55,1738,1741],{"href":1739,"rel":1740},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6473",[264],"PR-6473",[40,1743,1745],{"id":1744},"admin","Admin",[32,1747,1749],{"id":1748},"support-getting-a-message-by-message-id-in-pulsar-admin","Support getting a message by message ID in pulsar-admin",[48,1751,1752],{},"This PR adds a new command get-message-by-id to the pulsar-admin. It allows users to check a single message by providing ledger ID and entry ID.",[339,1754,1755],{},[342,1756,1133,1757,190],{},[55,1758,1761],{"href":1759,"rel":1760},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6331",[264],"PR-6331",[32,1763,1765],{"id":1764},"support-deleting-subscriptions-forcefully","Support deleting subscriptions forcefully",[48,1767,1768],{},"This PR adds the method deleteForcefully to support force deleting subscriptions.",[339,1770,1771],{},[342,1772,1133,1773,190],{},[55,1774,1777],{"href":1775,"rel":1776},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6383",[264],"PR-6383",[40,1779,1781],{"id":1780},"functions","Functions",[32,1783,1785],{"id":1784},"built-in-functions","Built-in functions",[48,1787,1788],{},"This PR implements the possibility of creating built-in functions in the same way as adding built-in connectors.",[339,1790,1791],{},[342,1792,1133,1793,190],{},[55,1794,1797],{"href":1795,"rel":1796},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6895",[264],"PR-6895",[32,1799,1801],{"id":1800},"add-go-function-heartbeat-and-grpc-service-for-production-usage","Add Go Function heartbeat (and gRPC service) for production usage",[339,1803,1804],{},[342,1805,1133,1806,190],{},[55,1807,1810],{"href":1808,"rel":1809},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6031",[264],"PR-6031",[32,1812,1814],{"id":1813},"add-custom-property-options-to-functions","Add custom property options to functions",[48,1816,1817],{},"This PR allows users to set custom system properties while submitting functions. This can be used to pass credentials via a system property.",[339,1819,1820],{},[342,1821,1133,1822,190],{},[55,1823,1826],{"href":1824,"rel":1825},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6348",[264],"PR-6348",[32,1828,1830],{"id":1829},"separate-tls-configurations-of-function-worker-and-broker","Separate TLS configurations of function worker and broker",[339,1832,1833],{},[342,1834,1133,1835,190],{},[55,1836,1839],{"href":1837,"rel":1838},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6602",[264],"PR-6602",[32,1841,1843],{"id":1842},"add-the-ability-to-build-consumers-in-functions-and-sources","Add the ability to build consumers in functions and sources",[48,1845,1846],{},"Previously, function and source context give their writers an ability to create publishers but not consumers. This PR fixes this issue.",[339,1848,1849],{},[342,1850,1133,1851,190],{},[55,1852,1855],{"href":1853,"rel":1854},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6954",[264],"PR-6954",[40,1857,1859],{"id":1858},"pulsar-sql","Pulsar SQL",[32,1861,1863],{"id":1862},"support-keyvalue-schema","Support KeyValue schema",[48,1865,1866],{},"Previously, Pulsar SQL could not read the KeyValue schema data.",[48,1868,1869],{},"This PR adds KeyValue schema support for Pulsar SQL. It adds the prefix key. for the key field name and value. for the value field name.",[339,1871,1872],{},[342,1873,1133,1874,190],{},[55,1875,1878],{"href":1876,"rel":1877},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6325",[264],"PR-6325",[32,1880,1882],{"id":1881},"support-multiple-avro-schema-versions","Support multiple Avro schema versions",[48,1884,1885],{},"Previously, if you have multiple Avro schema versions for a topic, using Pulsar SQL to query data from this topic introduces some problems. With this change, You can evolve the schema of the topic and keep transitive backward compatibility of all schemas of the topic if you want to query data from this topic.",[339,1887,1888],{},[342,1889,1133,1890,190],{},[55,1891,1894],{"href":1892,"rel":1893},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F4847",[264],"PR-4847",[40,1896,1898],{"id":1897},"java-client","Java client",[32,1900,1902],{"id":1901},"support-waiting-for-inflight-messages-while-closing-a-producer","Support waiting for inflight messages while closing a producer",[48,1904,1905],{},"Previously, when you closed a producer, pulsar-client immediately failed inflight messages even if they persisted successfully at the broker. Most of the time, users want to wait for those inflight messages rather than fail them. While pulsar-client lib did not provide a way to wait for inflight messages before closing the producer.",[48,1907,1908],{},"This PR supports closing API with the flag where you can control waiting for inflight messages. With this change, you can close a producer by waiting for inflight messages and pulsar-client does not fail those messages immediately.",[339,1910,1911],{},[342,1912,1133,1913,190],{},[55,1914,1917],{"href":1915,"rel":1916},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6648",[264],"PR-6648",[32,1919,1921],{"id":1920},"support-loading-tls-certskey-dynamically-from-input-stream","Support loading TLS certs\u002Fkey dynamically from input stream",[48,1923,1924],{},"Previously, pulsar-client provided TLS authentication support and default TLS provider AuthenticationTls expected file path of cert and key files. However, there were use cases where it was difficult for user applications to store certs\u002Fkey files locally for TLS authentication.",[48,1926,1927],{},"This PR adds stream support in AuthenticationTls to provide X509Certs and PrivateKey which also performs auto-refresh when streaming changes in a given provider.",[339,1929,1930],{},[342,1931,1133,1932,190],{},[55,1933,1936],{"href":1934,"rel":1935},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6760",[264],"PR-6760",[32,1938,1940],{"id":1939},"support-returning-sequence-id-when-throwing-an-exception-for-async-send-messages","Support returning sequence ID when throwing an exception for async send messages",[48,1942,1943],{},"Previously, when sending messages asynchronously failed, an exception was thrown, but did not know which message was abnormal, and users did not know which messages needed to be retried.",[48,1945,1946],{},"This PR makes changes supported on the client side. When throwing an exception, the sequenceId org.apache.pulsar.client.api.PulsarClientException is set.",[339,1948,1949],{},[342,1950,1133,1951,190],{},[55,1952,1955],{"href":1953,"rel":1954},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpull\u002F6825",[264],"PR-6825",[40,1957,1959],{"id":1958},"reference","Reference",[32,1961,1963],{"id":1962},"pulsar","Pulsar",[339,1965,1966,1973],{},[342,1967,1968,1969,190],{},"To download Apache Pulsar 2.6.0, click ",[55,1970,267],{"href":1971,"rel":1972},"https:\u002F\u002Fpulsar.apache.org\u002Fen\u002Fdownload\u002F",[264],[342,1974,1975,1976,1457,1981,190],{},"For more information about Apache Pulsar 2.6.0, see ",[55,1977,1980],{"href":1978,"rel":1979},"https:\u002F\u002Fpulsar.apache.org\u002Frelease-notes\u002F#2.6.0",[264],"2.6.0 release notes",[55,1982,1985],{"href":1983,"rel":1984},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar\u002Fpulls?q=milestone%3A2.6.0+-label%3Arelease%2F2.5.2+-label%3Arelease%2F2.5.1+",[264],"2.6.0 PR list",[48,1987,1988],{},"If you have any questions or suggestions, contact us by Pulsar mailing list or Slack.",[339,1990,1991,2002],{},[342,1992,1993,1994,1457,1998,190],{},"Pulsar mailing list: ",[55,1995,1997],{"href":1996},"mailto:users@pulsar.apache.org","users@pulsar.apache.org",[55,1999,2001],{"href":2000},"mailto:dev@pulsar.apache.org","dev@pulsar.apache.org",[342,2003,2004,2005,190],{},"Pulsar Slack: ",[55,2006,2007],{"href":2007,"rel":2008},"https:\u002F\u002Fapache-pulsar.slack.com\u002F",[264],[48,2010,2011,2012,190],{},"Looking forward to your contributions to ",[55,2013,1963],{"href":2014,"rel":2015},"https:\u002F\u002Fgithub.com\u002Fapache\u002Fpulsar",[264],[48,2017,2018,2019,190],{},"This post was originally published by Penghui Li on ",[55,2020,2023],{"href":2021,"rel":2022},"https:\u002F\u002Fpulsar.apache.org\u002Fblog\u002F2020\u002F06\u002F18\u002FApache-Pulsar-2-6-0\u002F",[264],"Apache Pulsar blog",[32,2025,2027],{"id":2026},"streamnative","StreamNative",[48,2029,2030,2031,2035,2036,190],{},"If you are interested in Pulsar community news, Pulsar development details, and Pulsar user stories on production, navigate to ",[55,2032,2034],{"href":2033},"\u002F","StreamNative website"," or follow ",[55,2037,2040],{"href":2038,"rel":2039},"https:\u002F\u002Ftwitter.com\u002Fstreamnativeio",[264],"@streamnativeio on Twitter",[48,2042,2043,2044,190],{},"If you are interested in Pulsar examples, demos, tools, and extensions, check out ",[55,2045,2048],{"href":2046,"rel":2047},"https:\u002F\u002Fgithub.com\u002Fstreamnative",[264],"StreamNative GitHub",[48,2050,2051],{},"Start your journey now with StreamNative!",{"title":18,"searchDepth":19,"depth":19,"links":2053},[2054,2091,2094,2098,2105,2109,2114],{"id":1100,"depth":19,"text":1101,"children":2055},[2056,2058,2060,2062,2064,2066,2068,2070,2072,2074,2076,2078,2080,2081,2082,2083,2084,2085,2086,2087,2088,2090],{"id":1104,"depth":279,"text":2057},"PIP-37 Large message size support",{"id":1141,"depth":279,"text":2059},"PIP-39 Namespace change events (system topic)",{"id":1170,"depth":279,"text":2061},"PIP-45 Pluggable metadata interface",{"id":1201,"depth":279,"text":2063},"PIP-54 Support acknowledgment at the batch index level",{"id":1233,"depth":279,"text":2065},"PIP-58 Support consumers setting custom message retry delay",{"id":1268,"depth":279,"text":2067},"PIP-60 Support SNI routing to support various proxy servers",{"id":1297,"depth":279,"text":2069},"PIP-61 Advertise multiple addresses",{"id":1338,"depth":279,"text":2071},"PIP-65 Adapt Pulsar IO sources to support BatchSources",{"id":1364,"depth":279,"text":2073},"Load balancer Add ThresholdShedder strategy for the load balancer",{"id":1398,"depth":279,"text":2075},"Key Shared Add consistent hashing in the Key_Shared distribution",{"id":1429,"depth":279,"text":2077},"Key Shared Fix ordering issue in KeyShared dispatcher when adding consumers",{"id":1465,"depth":279,"text":2079},"Key Shared Add support for key hash range reading",{"id":1492,"depth":279,"text":1493},{"id":1517,"depth":279,"text":1518},{"id":1542,"depth":279,"text":1543},{"id":1567,"depth":279,"text":1568},{"id":1589,"depth":279,"text":1590},{"id":1614,"depth":279,"text":1615},{"id":1642,"depth":279,"text":1643},{"id":1664,"depth":279,"text":1665},{"id":1686,"depth":279,"text":2089},"Schema Support null key and null value in KeyValue schema",{"id":1702,"depth":279,"text":1703},{"id":1721,"depth":19,"text":1722,"children":2092},[2093],{"id":1725,"depth":279,"text":1726},{"id":1744,"depth":19,"text":1745,"children":2095},[2096,2097],{"id":1748,"depth":279,"text":1749},{"id":1764,"depth":279,"text":1765},{"id":1780,"depth":19,"text":1781,"children":2099},[2100,2101,2102,2103,2104],{"id":1784,"depth":279,"text":1785},{"id":1800,"depth":279,"text":1801},{"id":1813,"depth":279,"text":1814},{"id":1829,"depth":279,"text":1830},{"id":1842,"depth":279,"text":1843},{"id":1858,"depth":19,"text":1859,"children":2106},[2107,2108],{"id":1862,"depth":279,"text":1863},{"id":1881,"depth":279,"text":1882},{"id":1897,"depth":19,"text":1898,"children":2110},[2111,2112,2113],{"id":1901,"depth":279,"text":1902},{"id":1920,"depth":279,"text":1921},{"id":1939,"depth":279,"text":1940},{"id":1958,"depth":19,"text":1959,"children":2115},[2116,2117],{"id":1962,"depth":279,"text":1963},{"id":2026,"depth":279,"text":2027},"Apache Pulsar","2020-06-18","Learn the most interesting and major features added to Pulsar 2.6.0.","\u002Fimgs\u002Fblogs\u002F63d798346c268e4f9c96ec60_63a3726cefd8ad294839867a_260-top.webp",{},"\u002Fblog\u002Fapache-pulsar-2-6-0","15 min read",{"title":1088,"description":2120},"blog\u002Fapache-pulsar-2-6-0",[302,2118],"pL2-555qS0x1R2hUHczXRabTqZlhN9sjS_KS4S9XSXs",[2130],{"id":2131,"title":313,"bioSummary":2132,"email":290,"extension":8,"image":2133,"linkedinUrl":2134,"meta":2135,"position":2142,"stem":2143,"twitterUrl":2144,"__hash__":2145},"authors\u002Fauthors\u002Fpenghui-li.md","Penghui Li is passionate about helping organizations to architect and implement messaging services. Prior to StreamNative, Penghui was a Software Engineer at Zhaopin.com, where he was the leading Pulsar advocate and helped the company adopt and implement the technology. He is an Apache Pulsar Committer and PMC member.","\u002Fimgs\u002Fauthors\u002Fpenghui-li.webp","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fpenghui-li-244173184\u002F",{"body":2136},{"type":15,"value":2137,"toc":2140},[2138],[48,2139,2132],{},{"title":18,"searchDepth":19,"depth":19,"links":2141},[],"Director of Streaming, StreamNative & Apache Pulsar PMC Member","authors\u002Fpenghui-li","https:\u002F\u002Ftwitter.com\u002Flipenghui6","WDjET7GfxqVQJ8mTEMaRhgpxRdDy18qZkgQDJlwjvbI",[2147,2155,2159],{"path":2148,"title":2149,"date":2150,"image":2151,"link":-1,"collection":2152,"resourceType":2153,"score":2154,"id":2148},"\u002Fblog\u002Fintroducing-streamnative-private-cloud","Introducing StreamNative Private Cloud","2023-11-07","\u002Fimgs\u002Fblogs\u002F65651a8ab3803cd436578980_Introducing-StreamNative-Private-Cloud.png","blogs","Blog",1,{"path":2156,"title":2157,"date":2158,"image":-1,"link":-1,"collection":2152,"resourceType":2153,"score":2154,"id":2156},"\u002Fblog\u002Fsecure-your-pulsar-cluster-with-revocable-api-keys","Secure Your Pulsar Cluster with Revocable API Keys","2023-10-24",{"path":2160,"title":2161,"date":2162,"image":2163,"link":-1,"collection":2152,"resourceType":2153,"score":2154,"id":2160},"\u002Fblog\u002Fapache-pulsar-3-1","Introducing Apache Pulsar 3.1","2023-10-01","\u002Fimgs\u002Fblogs\u002F653b0de15866dac5fbac0228_pulsar-1200-630.png",1775716415241]