Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Refine README and docker compose files in examples #489

Merged
merged 19 commits into from
Jan 18, 2024

Conversation

jovezhong
Copy link
Contributor

Refine the Proton top level README as well as various README and Docker Compose files in examples folder.

@jovezhong jovezhong marked this pull request as ready for review January 15, 2024 23:22
@yokofly
Copy link
Collaborator

yokofly commented Jan 16, 2024

Why we will run CI this time: 1. modify a new webp pic in design 2. remove a docker-compose yaml.
those are all unrelated things.

why CI failure: there was a PR forced merge but the test failed even when the PR merged.
thus waiting for this PR #477 to fix CI.

@jovezhong
Copy link
Contributor Author

Thank @yokofly

@jovezhong jovezhong requested a review from chenziliang January 16, 2024 04:17
@jovezhong jovezhong changed the title Refine README and examples docs: Refine README and docker compose files in examples Jan 16, 2024
- ./grafana_provisioning:/etc/grafana/provisioning
depends_on:
init-proton:
condition: service_completed_successfully
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may like to put another empty line after

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested all docker compose files. Without the empty line in the bottom, it can work, but I am not sure whether having the empty last line is a best practice or not. Maybe nice to have

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Saw some discussions https://stackoverflow.com/questions/2287967/why-is-it-recommended-to-have-empty-line-in-the-end-of-a-source-file More like to avoid unexpected errors for old tools.

tlsClientCert: ""
tlsClientKey: ""
version: 1
editable: true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

volumes:
- ./grafana_provisioning:/etc/grafana/provisioning
depends_on:
- proton
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

# <string, required> path to dashboard files on disk. Required when using the 'file' type
path: /etc/grafana/provisioning/dashboards
# <bool> use folder names from filesystem to create folders in Grafana
foldersFromFilesStructure: true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here and for others

README.md Outdated
Proton is a unified streaming and historical data analytics database in a single binary. It helps data engineers and platform engineers solve complex real-time analytics use cases, and powers the [Timeplus](https://timeplus.com) streaming analytics platform.
1. **[Apache Flink](https://github.com/apache/flink) or [ksqlDB](https://github.com/confluentinc/ksql) alternative.** Proton provides powerful streaming SQL functionalities, such as streaming ETL, tumble/hop/session windows, watermarks, materialized views, CDC and data revision processing, and more.
2. **Fast.** Proton is written in C++, with optimized performance through SIMD. [For example](https://www.timeplus.com/post/scary-fast), on an Apple MacBookPro with M2 Max, Proton can deliver 90 million EPS, 4 millisecond end-to-end latency, and high cardinality aggregation with 1 million unique keys.
3. **Lightweight.** Proton is a single binary (\<500MB). No JVM or any other dependencies. You can also run it with Docker, or on an AWS t2.nano instance (1 vCPU and 0.5 GiB memory).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need mention 500MB here ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<500MB is not a bad number, but yes, this is optional but doesn't hurt. Comparing to other solutions, we are still relatively small size

@jovezhong jovezhong requested a review from tingfirst January 16, 2024 21:11
@CLAassistant
Copy link

CLAassistant commented Jan 17, 2024

CLA assistant check
All committers have signed the CLA.

@jovezhong jovezhong merged commit e5a0501 into develop Jan 18, 2024
3 of 10 checks passed
@jovezhong jovezhong deleted the feature/issue-14-better-readme-3 branch February 23, 2024 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants