micro-cluster | Run multiple micro servers and a front proxy at a time | Microservice library

 by   vercel JavaScript Version: 1.0.0 License: MIT

kandi X-RAY | micro-cluster Summary

kandi X-RAY | micro-cluster Summary

micro-cluster is a JavaScript library typically used in Architecture, Microservice, Docker, Prometheus applications. micro-cluster has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Run multiple micro servers and a front proxy at a time
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              micro-cluster has a low active ecosystem.
              It has 174 star(s) with 17 fork(s). There are 8 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 5 open issues and 0 have been closed. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of micro-cluster is 1.0.0

            kandi-Quality Quality

              micro-cluster has 0 bugs and 0 code smells.

            kandi-Security Security

              micro-cluster has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              micro-cluster code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              micro-cluster is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              micro-cluster releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of micro-cluster
            Get all kandi verified functions for this library.

            micro-cluster Key Features

            No Key Features are available at this moment for micro-cluster.

            micro-cluster Examples and Code Snippets

            No Code Snippets are available at this moment for micro-cluster.

            Community Discussions

            QUESTION

            Elasticsearch mega-cluster vs smaller clusters when you have relatively small amounts of data
            Asked 2020-Sep-25 at 00:28

            At the moment we have 3 separate environments, with 4 Elasticsearch clusters. More over we have 2 different use cases, whereby we search through customer data for similarities, and we have logs which we search through.

            Reading the elasticsearch documentation and online video discussions it is recommended to optimise your cluster for your use case, so technically speaking we should have then 4 x 2 = 8 separate clusters. Some clusters could be grouped together on the basis of being production and non-production clusters. But really we are a small team, < 10 people, there isn't allot of data in most of these clusters, so it is too expensive to run 3 x master nodes in all of them.

            Even though Elastic seem to recommend to have one cluster per use case so you can optimise your index & shard size IMO I believe we would be getting much better performance and stability if we only had the 1 cluster, or at least went down to 2 (prod & nonprod). We'd also have less maintenance overheads I'm getting CloudWatch alarms in every environment, there are saved objects which are needing to be transferred from on environment to another, and I have become the person to mange all this which ends up creating allot of dead effort.

            So my question is even though clusters should be tuned per use-case for best practice, Does this still make sense when your data is only a couple of GiB? Given the overhead in management, and the stability trade-offs with micro-clusters that don't have master nodes?

            ...

            ANSWER

            Answered 2020-Aug-12 at 06:35

            ES clusters are made of nodes(data and master nodes most importantly) and its not like that you can optimize only at cluster level, you can easily fine tune the index and shards level based on your use-case.

            As in your case you don't have much data it makes sense to have just 2 env(prod and non-prod env.) to avoid the cluster management overhead and to apply the best practice like having 3 master nodes for high availability reasons.

            when it comes to optimize based on what data and use-case your indices are severing, you can optimize that, for example for read-heavy indices it makes sense to have more replicas and for index heavy operations, you might want to increase the refresh_interval(def 1 sec) to higher value.

            Refer improve search performance and improve indexing speed for tunning your indices and you can also try free cluster analyzer tool to find the bad configuration in your cluster and nodes.

            Source https://stackoverflow.com/questions/63369679

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install micro-cluster

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/vercel/micro-cluster.git

          • CLI

            gh repo clone vercel/micro-cluster

          • sshUrl

            git@github.com:vercel/micro-cluster.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link