This is an automated email from the ASF dual-hosted git repository.

lhotari pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new f0a3693e7f5f Minor improvements to the blog post
f0a3693e7f5f is described below

commit f0a3693e7f5fd6ebff2dc80513f6129cfcdd7a6f
Author: Lari Hotari <[email protected]>
AuthorDate: Fri Oct 25 23:09:00 2024 +0300

    Minor improvements to the blog post
---
 blog/2024-10-24-announcing-apache-pulsar-4-0.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/blog/2024-10-24-announcing-apache-pulsar-4-0.md 
b/blog/2024-10-24-announcing-apache-pulsar-4-0.md
index 814d7ec67e17..ebc919afa8c6 100644
--- a/blog/2024-10-24-announcing-apache-pulsar-4-0.md
+++ b/blog/2024-10-24-announcing-apache-pulsar-4-0.md
@@ -37,14 +37,13 @@ The Docker images now include Java 21 with Generational 
ZGC, bringing significan
 
 These improvements make Pulsar 4.0's Docker runtime an even more compelling 
choice for organizations requiring both security and performance in their 
messaging infrastructure. The combination of Alpine Linux's minimal attack 
surface and Java 21's advanced garbage collection provides a robust foundation 
for running Pulsar in containerized environments.
 
-
 ### Enhanced Quality of Service (QoS) Controls
 
 Multi-tenancy in messaging systems presents unique architectural challenges, 
particularly around resource isolation and predictable performance. Apache 
Pulsar's approach to this has centered on providing granular control over 
system resources while maintaining consistency across tenant workloads.
 
 The core advancement in Pulsar 4.0 comes through [PIP-322 Pulsar Rate Limiting 
Refactoring](https://github.com/apache/pulsar/blob/master/pip/pip-322.md). At 
its foundation is a token bucket algorithm implementation that unifies rate 
limiting across broker, topic, and resource group levels. This eliminates the 
previous split between "default" and "precise" rate limiters—a design choice 
that had introduced unnecessary CPU overhead and lock contention in IO threads.
 
-The practical impact is straightforward: more predictable performance in 
multi-tenant deployments, especially when multiple rate limiting conditions 
intersect. The community is already building on this foundation with 
[PIP-385](https://lists.apache.org/thread/9wddmj4o5mrdst427r40rr7phqb05y6s), 
which addresses producer flow control — a key piece in completing Pulsar's 
end-to-end QoS capabilities.
+The practical impact is straightforward: more predictable performance in 
multi-tenant deployments, especially when multiple rate limiting conditions 
intersect. While Pulsar already supports producer rate limiting, the community 
is building on this foundation with 
[PIP-385](https://lists.apache.org/thread/9wddmj4o5mrdst427r40rr7phqb05y6s) to 
improve producer flow control —a key piece in completing Pulsar's end-to-end 
QoS capabilities.
 
 #### Rate Limiting and Capacity Management in Modern Messaging Platforms
 
@@ -103,4 +102,4 @@ We extend our deepest gratitude to:
 
 The project faces typical open-source challenges — we're operating with a 
volunteer workforce and currently experiencing a backlog in pull request 
reviews. While this is a common scenario in successful Apache projects, we're 
actively working on processes to handle contributions more efficiently.
 
-Apache Pulsar's strength lies in its community-driven development. Whether 
you're running Pulsar in production or evaluating it for your technology stack, 
we encourage you to join the conversation on the 
[[email protected]](mailto:[email protected]) mailing list or the 
[Pulsar Slack community](https://apache-pulsar.slack.com/). Your experience and 
feedback help shape the future of this platform.
\ No newline at end of file
+Apache Pulsar's strength lies in its community-driven development. Whether 
you're running Pulsar in production or evaluating it for your technology stack, 
we encourage you to join the conversation on the 
[[email protected]](https://pulsar.apache.org/contact/#mailing-lists) 
mailing list or the [Pulsar Slack 
community](https://pulsar.apache.org/community/#section-discussions). Your 
experience and feedback help shape the future of this platform.
\ No newline at end of file

Reply via email to