You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/12/29 22:48:26 UTC
[GitHub] [pulsar-site] DaveDuggins opened a new pull request, #349: [doc][improve] Update Pulsar site landing page .js files and images
DaveDuggins opened a new pull request, #349:
URL: https://github.com/apache/pulsar-site/pull/349
The Pulsar site landing page (https://pulsar.apache.org/) is comprised of Javascript elements culled from several files, one of which links to an asset repo. To refresh the content on this page, the files in the commit list below were updated as indicated.
Local preview does not pick up the new content. Is this because the Javascript is executed serverside, and so won't launch until after the new content is pushed?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "asafm (via GitHub)" <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1083424723
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Review Comment:
@DaveDuggins Can you please update the title and content per my comment above?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1066336102
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
+ Svg: require("../../static/img/1-M-topics.svg").default,
Review Comment:
This correction has been added to the PR.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1063013629
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
+ Svg: require("../../static/img/1-M-topics.svg").default,
Review Comment:
All the rest of the topic titles are short -- a single word or phrase. Full sentences don't match. We could add "in a single cluster" but we don't want full sentences for one description and not for the others.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by GitBox <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1383097360
> I'm not sure the best format for this discussion, but in my opinion, I think we need to discuss the motivation for changing the top level feature list @DaveDuggins. There are some fundamental changes here.
I pasted the context/motivation for changing it also in the mailing list to open it up for discussion.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by GitBox <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1070543002
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Review Comment:
Thanks for the clarification, @michaeljmarshall. How about we'll write it as such:
**Durable low-latency messaging and streaming**
Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms). Message durability is achieved using Bookkeeper as a storage layer and Cloud-based tiered storage.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] momo-jun commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
momo-jun commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1376647073
@urfreespace, thanks for looking into this and pointing out the issue.
@DaveDuggins, the changes made in the `docusaurus.config.js` file only update the bottom of the site as follows.
<img width="909" alt="image" src="https://user-images.githubusercontent.com/60642177/211449252-14051cc9-fd2d-4ffe-8740-6d52d24e7fb6.png">
I'm not sure whether this is expected, but I guess the intentional change should be like the following, correct? I updated the `index.js` file, and the preview shows.
<img width="877" alt="image" src="https://user-images.githubusercontent.com/60642177/211449004-08e94c5c-5322-43a2-a390-dacec79f68ad.png">
Pls let us know whether the two updates are both required. Then the PR is good to go.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] momo-jun commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
momo-jun commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1374706225
@tisonkun thanks for the fix.
@DaveDuggins I attached the screenshots of my local preview. You can check it out and see whether it is expected or still needs adjustments.
<img width="1225" alt="image" src="https://user-images.githubusercontent.com/60642177/211180478-8622c00a-9334-468c-9300-54cd3470990c.png">
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] urfreespace commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
urfreespace commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1376591819
@momo-jun I do a test, and the problem is not happening, perhaps you could relaunch your local preview again.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "michaeljmarshall (via GitHub)" <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1084390828
##########
src/pages/index.js:
##########
@@ -191,7 +190,9 @@ export default function Home() {
/>
<SubHeroBlock
heading="What is Apache Pulsar?"
- content="Apache Pulsar is a cloud-native, multi-tenant, high-performance solution for server-to-server messaging and queuing built on the publisher-subscribe (pub-sub) pattern. Pulsar combines the best features of a traditional messaging system like RabbitMQ with those of a pub-sub system like Apache Kafka – scaling up or down dynamically without downtime. It's used by thousands of companies for high-performance data pipelines, microservices, instant messaging, data integrations, and more."
+ content="Apache Pulsar is an all-in-one messaging and streaming platform. Messages can be consumed and acknowledged individually or consumed as streams with less than 5ms of latency. Its layered architecture allows rapid scaling across hundreds of nodes, without data reshuffling. Its features include multi-tenancy with resource separation and access control, geo-replication across regions, tiered storage and support for five official client languages. It supports up to one million unique topics and is designed to simplify your application architecture.
+
+Pulsar is a Top 10 Apache Software Foundation project and has a vibrant and passionate community and user base spanning small companies and large enterprises."
Review Comment:
I mention it because it justifies the claim. Also, that blog post quantifies how it measures Apache Pulsar as one of the top 10 projects. I am not sure it is strictly necessary, though.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] Anonymitaet commented on pull request #349: [doc][improve] Update Pulsar site landing page .js files and images
Posted by GitBox <gi...@apache.org>.
Anonymitaet commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1367666902
Could you please attach the screenshots of the local preview? You can follow the steps [here](https://pulsar.apache.org/contribute/document-preview/#preview-website-changes)
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1374776161
@DaveDuggins, Can you please change the title and summary to reflect the content and intent of this PR? I think another PR you had got the description and title mixed into here by mistake.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] dave2wave commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
dave2wave commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1376695031
This is an interesting change being proposed. Since it changes the messaging of the main Pulsar website can we please solicit comments from the community on dev@pulsar.apache.org before committing this change.
FYI - the official mission in the ASF Board Resolution establishing the Apache Pulsar PMC is "highly scalable, low latency messaging platform running on commodity hardware". Let's be careful with changing our mission.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
michaeljmarshall commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1377572844
> @DaveDuggins, Can you please change the title and summary to reflect the content and intent of this PR? I think another PR you had got the description and title mixed into here by mistake.
Great point @asafm. Please make sure to update the PR description @DaveDuggins with the intended changes and the justification for these changes.
I also agree with @dave2wave that we need discuss many of the changes proposed in this PR on the dev mailing list.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "michaeljmarshall (via GitHub)" <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1084383786
##########
src/pages/index.js:
##########
@@ -191,7 +190,9 @@ export default function Home() {
/>
<SubHeroBlock
heading="What is Apache Pulsar?"
- content="Apache Pulsar is a cloud-native, multi-tenant, high-performance solution for server-to-server messaging and queuing built on the publisher-subscribe (pub-sub) pattern. Pulsar combines the best features of a traditional messaging system like RabbitMQ with those of a pub-sub system like Apache Kafka – scaling up or down dynamically without downtime. It's used by thousands of companies for high-performance data pipelines, microservices, instant messaging, data integrations, and more."
+ content="Apache Pulsar is an all-in-one messaging and streaming platform. Messages can be consumed and acknowledged individually or consumed as streams with less than 5ms of latency. Its layered architecture allows rapid scaling across hundreds of nodes, without data reshuffling. Its features include multi-tenancy with resource separation and access control, geo-replication across regions, tiered storage and support for five official client languages. It supports up to one million unique topics and is designed to simplify your application architecture.
+
+Pulsar is a Top 10 Apache Software Foundation project and has a vibrant and passionate community and user base spanning small companies and large enterprises."
Review Comment:
Yes, that's the link I was referencing.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "michaeljmarshall (via GitHub)" <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1084385229
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party-integrations.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
Review Comment:
Yes, I think that would be a good dev/user mailing list discussion. It could probably start on the dev list. I haven't run with that many topics before, either.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1066043523
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Review Comment:
This removes "durability" without adding it somewhere else. I view durability as an essential guarantee.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
Review Comment:
This removes `Persistent` without replacing it. The fact that Apache Pulsar persists data is fundamental and ought to be on our main page.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by GitBox <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1070543525
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
Review Comment:
Perhaps the changes proposed to previous comments lead the reader to understand that data is persisted since it's durable?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page .js files and images
Posted by GitBox <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1059876488
##########
docusaurus.config.js:
##########
@@ -288,7 +288,7 @@ module.exports = {
items: [
{
html: `<div><small><strong>Apache Pulsar is available under the <a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License, version 2.0.</a></strong></small></div>
- <div>Apache Pulsar is a distributed, open source pub-sub messaging and streaming platform for real-time workloads, managing hundreds of billions of events per day.</div>`,
+ <div>Apache Pulsar is an open-source, distributed messaging and streaming platform built for the cloud.</div>`,
Review Comment:
You forgot to change the headline "Cloud-Native messaging and streaming platform"
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
+ Svg: require("../../static/img/1-M-topics.svg").default,
Review Comment:
There's a big mistake here. The text should have been:
Pulsar's unique architecture supports up to 1 million topics in a single cluster. Simplify your own architecture by avoiding multiplexing multiple streams into a single topic.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
Review Comment:
If this fix is to be inserted, the same needs to be done for "Official 3rd party integrations".
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page .js files and images
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1061063174
##########
docusaurus.config.js:
##########
@@ -288,7 +288,7 @@ module.exports = {
items: [
{
html: `<div><small><strong>Apache Pulsar is available under the <a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License, version 2.0.</a></strong></small></div>
- <div>Apache Pulsar is a distributed, open source pub-sub messaging and streaming platform for real-time workloads, managing hundreds of billions of events per day.</div>`,
+ <div>Apache Pulsar is an open-source, distributed messaging and streaming platform built for the cloud.</div>`,
Review Comment:
I did change it. It's in another module.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] merlimat merged pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "merlimat (via GitHub)" <gi...@apache.org>.
merlimat merged PR #349:
URL: https://github.com/apache/pulsar-site/pull/349
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] Anonymitaet commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
Anonymitaet commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1373054994
Hi @DaveDuggins could you please address commenters' concerns? After that we can merge this PR, thank you!
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1374776374
@momo-jun There should be other screenshots as 3 sections were changed
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] momo-jun commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
momo-jun commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1374830527
@asafm thanks for the reminder. I attached two more screenshots.
The `index.js` update works as follows.
<img width="943" alt="image" src="https://user-images.githubusercontent.com/60642177/211197143-0234d989-03a1-4735-bab9-bf5aadd19ad5.png">
However, the `docusaurus.config.js` update doesn't show in the local preview. @tisonkun Did you know the cause?
<img width="976" alt="image" src="https://user-images.githubusercontent.com/60642177/211197136-d9647c32-2e4b-4147-8567-19e25070282e.png">
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1377847795
> @DaveDuggins, Can you please change the title and summary to reflect the content and intent of this PR? I think another PR you had got the description and title mixed into here by mistake.
Is the title you're seeing "Update Pulsar site landing page content?" Because that is exactly what this PR is doing.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
tisonkun commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1373391394
FYI I pushed a commit 5d335be2c6b3351dbc63ae3845ced1c6869fb123 to fix the broken links. @DaveDuggins please ensure previews look good before requesting review :)
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page .js files and images
Posted by GitBox <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1061176849
##########
docusaurus.config.js:
##########
@@ -288,7 +288,7 @@ module.exports = {
items: [
{
html: `<div><small><strong>Apache Pulsar is available under the <a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License, version 2.0.</a></strong></small></div>
- <div>Apache Pulsar is a distributed, open source pub-sub messaging and streaming platform for real-time workloads, managing hundreds of billions of events per day.</div>`,
+ <div>Apache Pulsar is an open-source, distributed messaging and streaming platform built for the cloud.</div>`,
Review Comment:
Can you link? I can't find it.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1380329239
@dave2wave Sorry about that, I'll start the discussion in the mailing list.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "asafm (via GitHub)" <gi...@apache.org>.
asafm commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1083426955
##########
src/pages/index.js:
##########
@@ -191,7 +190,9 @@ export default function Home() {
/>
<SubHeroBlock
heading="What is Apache Pulsar?"
- content="Apache Pulsar is a cloud-native, multi-tenant, high-performance solution for server-to-server messaging and queuing built on the publisher-subscribe (pub-sub) pattern. Pulsar combines the best features of a traditional messaging system like RabbitMQ with those of a pub-sub system like Apache Kafka – scaling up or down dynamically without downtime. It's used by thousands of companies for high-performance data pipelines, microservices, instant messaging, data integrations, and more."
+ content="Apache Pulsar is an all-in-one messaging and streaming platform. Messages can be consumed and acknowledged individually or consumed as streams with less than 5ms of latency. Its layered architecture allows rapid scaling across hundreds of nodes, without data reshuffling. Its features include multi-tenancy with resource separation and access control, geo-replication across regions, tiered storage and support for five official client languages. It supports up to one million unique topics and is designed to simplify your application architecture.
+
+Pulsar is a Top 10 Apache Software Foundation project and has a vibrant and passionate community and user base spanning small companies and large enterprises."
Review Comment:
@michaeljmarshall You mean this one? https://news.apache.org/foundation/entry/apache-in-2021-by-the, where we can see pulsar is number 5th by number of commits?
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party-integrations.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
Review Comment:
I think it's a fascinating topic - let's try to get this from the dev/user mailing list ? I personally don't have that much experience with it.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
Review Comment:
My plan is to add a Features page, and for there we also list other features which were not highlighted, among them Granular Access Control which will detail also that pulsar support multiple authentication framework.
In that page we will devote 1-2 large paragraphs for each feature, therefore having the luxury to expand on it.
The way I picture it: Elevator pitch in the beginning will get 10sec attention. Next is the into paragraph, 30 sec attention. Next is the highlighted features, getting us 2-3min attention. Hence, I really try to avoid cognitive overload here and try to focus on the core differentiators and strengths of Pulsar in this landscape.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "michaeljmarshall (via GitHub)" <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1084387251
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
Review Comment:
That makes sense to me. Realistically, authentication frameworks are typically a secondary question, as your ordering suggests.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "asafm (via GitHub)" <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1400899181
@momo-jun I think we can merge 🥳
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by "michaeljmarshall (via GitHub)" <gi...@apache.org>.
michaeljmarshall commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1082919747
##########
src/pages/index.js:
##########
@@ -191,7 +190,9 @@ export default function Home() {
/>
<SubHeroBlock
heading="What is Apache Pulsar?"
- content="Apache Pulsar is a cloud-native, multi-tenant, high-performance solution for server-to-server messaging and queuing built on the publisher-subscribe (pub-sub) pattern. Pulsar combines the best features of a traditional messaging system like RabbitMQ with those of a pub-sub system like Apache Kafka – scaling up or down dynamically without downtime. It's used by thousands of companies for high-performance data pipelines, microservices, instant messaging, data integrations, and more."
+ content="Apache Pulsar is an all-in-one messaging and streaming platform. Messages can be consumed and acknowledged individually or consumed as streams with less than 5ms of latency. Its layered architecture allows rapid scaling across hundreds of nodes, without data reshuffling. Its features include multi-tenancy with resource separation and access control, geo-replication across regions, tiered storage and support for five official client languages. It supports up to one million unique topics and is designed to simplify your application architecture.
+
+Pulsar is a Top 10 Apache Software Foundation project and has a vibrant and passionate community and user base spanning small companies and large enterprises."
Review Comment:
What do you think about linking this claim to the ASF blog post?
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party-integrations.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
Review Comment:
It's out of the scope of this PR, but I wonder if we should provide users with a reference architecture to better understand how they can achieve the 1M topics. Maybe it could be a "cookbook". One reason I mention this is because a user might be interested to know how many nodes are required to achieve this high number of topics.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
Review Comment:
Yes, if we update the earlier section to add durable back, I think that is sufficient.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Review Comment:
Thanks for revisiting this. I think adding durability back takes care of my concerns.
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
Review Comment:
Is it worth mentioning that Pulsar supports multiple authentication frameworks?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1063022910
##########
docusaurus.config.js:
##########
@@ -288,7 +288,7 @@ module.exports = {
items: [
{
html: `<div><small><strong>Apache Pulsar is available under the <a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License, version 2.0.</a></strong></small></div>
- <div>Apache Pulsar is a distributed, open source pub-sub messaging and streaming platform for real-time workloads, managing hundreds of billions of events per day.</div>`,
+ <div>Apache Pulsar is an open-source, distributed messaging and streaming platform built for the cloud.</div>`,
Review Comment:
Fixed.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1063016647
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
+ Svg: require("../../static/img/official-3rd-party.svg").default,
+ content: "Pulsar has officially maintained connectors with popular 3rd parties: MySQL, Elasticsearch, Cassandra, and more. Allows streaming data in (source) or out (sink).",
},
{
- title: "Operability",
- Svg: require("../../static/img/operability.svg").default,
+ title: "Supports up to 1M topics",
+ Svg: require("../../static/img/1-M-topics.svg").default,
Review Comment:
My mistake, I see what you mean now.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] dave2wave commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
dave2wave commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1066155855
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
Review Comment:
"Official" seems to be unnecessary.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] DaveDuggins commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page content
Posted by GitBox <gi...@apache.org>.
DaveDuggins commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1066343758
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
},
{
- title: "Client libraries",
- Svg: require("../../static/img/client-libraries.svg").default,
- content: "Flexible messaging models with high-level APIs for Java, Go, Python, C++, Node.js, WebSocket and C#.",
+ title: "Official 3rd party integrations",
Review Comment:
We'll iterate after publishing.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] asafm commented on pull request #349: [doc][improve] Improve landing page 3 first sections
Posted by GitBox <gi...@apache.org>.
asafm commented on PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#issuecomment-1383096720
> > @DaveDuggins, Can you please change the title and summary to reflect the content and intent of this PR? I think another PR you had got the description and title mixed into here by mistake.
>
> Great point @asafm. Please make sure to update the PR description @DaveDuggins with the intended changes and the justification for these changes.
>
> I also agree with @dave2wave that we need discuss many of the changes proposed in this PR on the dev mailing list.
@michaeljmarshall , @DaveDuggins updated the PR with the original description that should have been there but was mixed out. I'll paste that context on the mailing list thread @dave2wave already opened.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] momo-jun commented on a diff in pull request #349: [doc][improve] Update Pulsar site landing page .js files and images
Posted by GitBox <gi...@apache.org>.
momo-jun commented on code in PR #349:
URL: https://github.com/apache/pulsar-site/pull/349#discussion_r1059224005
##########
src/components/HomepageFeatures.js:
##########
@@ -4,48 +4,48 @@ import ReactMarkdown from "react-markdown";
const FeatureList = (language) => [
{
- title: "Cloud-native",
- Svg: require("../../static/img/Technology-Solution.svg").default,
- content: "A multiple layer approach separating compute from storage to work with cloud infrastructures and Kubernetes.",
+ title: "Automatic Load Balancing",
+ Svg: require("../../static/img/automatic-load-balancing.svg").default,
+ content: "Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.",
},
{
title: "Serverless functions",
Svg: require("../../static/img/proven-in-production.svg").default,
- content:"Write serverless functions with developer-friendly APIs to natively process data immediately upon arrival. No need to run your own stream processing engine.",
+ content:"Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.",
},
{
- title: "Horizontally scalable",
+ title: "Rapid Horizontal Scalability",
Svg: require("../../static/img/horizontally-scalable.svg").default,
- content: "Expand capacity seamlessly to hundreds of nodes.",
+ content: "Scales horizontally to handle the increased load. Its unique design and separate storage layer enable handling the sudden surge in traffic by scaling out in seconds.",
},
{
- title: "Low latency with durability",
+ title: "Low-latency messaging and streaming",
Svg: require("../../static/img/low-latency.svg").default,
- content:"Low publish latency (< 5ms) at scale with strong durability guarantees.",
+ content:"Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at very large scales (hundreds of nodes) and low latency (<5ms).",
},
{
- title: "Geo-replication",
+ title: "Seamless Geo-Replication",
Svg: require("../../static/img/geo-replication.svg").default,
- content: "Configurable replication between data centers across multiple geographic regions.",
+ content: "Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.",
},
{
title: "Multi-tenancy",
Svg: require("../../static/img/multi-tenancy.svg").default,
- content:"Built from the ground up as a multi-tenant system. Supports isolation, authentication, authorization, and quotas.",
+ content:"Maintain one cluster for your entire organization using tenants. Access control across data and actions using tenant policies. Isolate specific brokers to a tenant when maximum noisy neighbor protection is needed.",
},
{
- title: "Persistent storage",
+ title: "Official multi-language support",
Svg: require("../../static/img/persistent-storage.svg").default,
- content:"Persistent message storage based on Apache BookKeeper. IO-level isolation between write, and read operations.",
+ content:"Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
Review Comment:
```suggestion
content:"Officially maintain Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.",
```
Use the present tense?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org