Anonymitaet commented on code in PR #398:
URL: https://github.com/apache/pulsar-site/pull/398#discussion_r1094168307


##########
blog/2023-02-03-apache-pulsar-hits-its-600th-contributor.md:
##########
@@ -0,0 +1,55 @@
+---
+author: Sherlock Xu
+title: "Apache Pulsar Hits Its 600th Contributor"
+date: 2023-02-03
+---
+
+![](/img/apache-pulsar-hits-its-600th-contributor.png)
+
+The Apache Pulsar community embraced a significant milestone last month as the 
project witnessed its 600th contributor to the [Pulsar main GitHub 
repository](https://github.com/apache/pulsar). We would like to thank everyone 
in the Pulsar community who contributed to this remarkable achievement.
+
+<!--truncate-->
+
+Since Pulsar’s graduation as a Top-Level Project (TLP) in September 2018, it 
has been driven by an active global community, with **160+** releases, **11K+** 
commits from **600** contributors, **12.2K+** stars, **3.2K+** forks, and 
**9600+** Slack users.
+
+## Strong community growth
+
+### 600 contributors
+
+The number of contributors is an important metric to measure the health of an 
open-source project. In the last year alone, we added almost 130 contributors 
to the project, a 28% increase from the previous year. The image below shows 
the number of Pulsar contributors over the past 6 years.
+
+![](/img/pulsar-total-contributors-202301.jpg)
+
+<center>Figure 1. Pulsar GitHub contributors</center>
+
+### Monthly active contributors of Pulsar and Kafka
+
+Both Pulsar and Kafka are popular streaming systems with contributors across 
the globe and are adopted by organizations spanning different industries. 
Although Kafka outnumbers Pulsar in the total number of contributors, the 
latter surpassed the former in terms of monthly active contributors about 2 
years ago and has maintained a strong momentum since then.
+
+![](/img/pulsar-kafka-monthly-active-contributors-202301.jpg)
+
+<center>Figure 2. Pulsar vs. Kafka - Monthly active contributors</center>
+
+### 12K+ GitHub stars
+
+GitHub stars are another key metric for open-source projects. Figure 3 
displays the star history of Pulsar since its inception.
+
+![](/img/pulsar-github-star-history-202301.png)
+
+<center>Figure 3. Pulsar GitHub stars</center>
+
+## Pulsar adoption
+
+As the project achieves strong growth in contributors, it also sees widespread 
adoption by companies across industries. Their success stories speak volumes 
about a more stable and secure project capable of powering different use cases 
in the messaging and streaming space.
+
+Pulsar has played an essential role in handling mission-critical workloads for 
both existing and new users. Tencent, one of the earliest companies to adopt 
Pulsar in production, has been consistently working to [improve the project for 
better 
stability](https://streamnative.io/blog/600k-topics-per-cluster-stability-optimization-apache-pulsar-tencent-cloud)
 and [shared their experience of handling 100 billion messages per 
day](https://streamnative.io/blog/client-optimization-how-tencent-maintains-apache-pulsar-clusters-100-billion-messages-daily).
 New adopters include Nippon Telegraph and Telephone Corporation (NTT) Software 
Innovation Center, which [uses a single Pulsar topic to handle 100K consumers 
for its IoT use 
case](https://streamnative.io/blog/handling-100k-consumers-with-one-pulsar-topic).
 Some organizations migrated from systems like Kafka to Pulsar, such as [Sina 
Weibo](https://streamnative.io/success-stories/sina-weibo) and 
[mParticle](https://www.mparticle.com/blog/apach
 e-pulsar-migration/). They select Pulsar not just for its flexibility, 
scalability, high availability, and unique architecture. More importantly, 
Pulsar solves the problems and pain points where other systems fall short.
+
+For more information, see this [list of companies using or contributing to 
Pulsar](pathname:///powered-by/) and check out [how different organizations are 
using Pulsar](pathname:///case-studies/).

Review Comment:
   Have you tested all the links in this blog?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to