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

Cluster #936

Open
mocaraka opened this issue Dec 2, 2023 · 4 comments
Open

Cluster #936

mocaraka opened this issue Dec 2, 2023 · 4 comments

Comments

@mocaraka
Copy link

mocaraka commented Dec 2, 2023

How long is expected to be merged into the main branch and tagged?

@fast01
Copy link

fast01 commented Dec 19, 2023

same questions,what's the status for now ?

@hengfeiyang
Copy link
Contributor

Cluster feature is paused

@andrewarrow
Copy link

andrewarrow commented Jan 21, 2024

just keep renting a bigger and bigger VM with tons of ram and hard drive space and cpu. Scale the old fashion way like ebay did for years:

The largest single VM you can rent from AWS in terms of CPU, RAM, and drive space is the Amazon EC2 P3dn.24xlarge instance. It provides 96 custom Intel Xeon Scalable vCPUs, 768 GiB of memory, and 1.8 TB of local NVMe-based SSD storage

@gedw99
Copy link

gedw99 commented Aug 23, 2024

If you want to cluster, you can just use NATS Jetstream in front and have all Set requests be forward to all the Zinc Servers.

For a Get, just use a NATS Queue pattern and it will hit one of the Zinc Servers.

NATS Jetstream can keep track of all Zinc Servers, by just wrapping Zinc with nats.go.

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

No branches or pull requests

5 participants