Results for cluster-magic

run multi-threaded node.js network applications using the native cluster module

Modify strings, generate sourcemaps

Generates CRC hashes for strings - for use by node redis clients to determine key slots.

Some useful utilities I often need

Find the position of grapheme cluster breaks in a string

A compiled-away, type-safe, readable RegExp alternative

magic-string with AST shortcut.

A collection of utilities for working with JSON objects, including diffing, conflict resolution, bundling and more.

Detect Filetype by bytes

Client for prometheus

Fast nd point clustering.

React-leaflet-cluster is a plugin for react-leaflet. A wrapper component of Leaflet.markercluster.

Cluster management for puppeteer

Group points into clusters based on their spatial proximity or properties.

AWS SDK for JavaScript Ecs Client for Node.js, Browser and React Native

Terminal and Web console for Kubernetes

Checks for URLs during typing and pasting and automatically converts them to links.

Magically drag and drop files/links, built for React

Takes a set of points and partition them into clusters according to DBSCAN's data clustering algorithm.

Sharing Connection among Multi-Process Nodejs

Core typings for Magic SDK packages.

cluster workers reload

Provides Beautiful Animated Marker Clustering functionality for Leaflet

Core business logic for Magic SDK packages.

Redis::Directory assumes a Redis installation running on a default port and database 0 that will contain connection information for various other Redis databases. For example, if you were using a Redis database to store the content of cached pages, and this was running on a cluster of two Redis instances, with multiple applications connecting partitioned by database, then your connection might look like this: require "redis" require "redis/distributed" # The ACME Corp database is #27 cache = Redis::Distributed.new "redis://redis.example:4400/27", "redis://redis.example:4401/27" Redis::Directory uses a centralized Redis database to store the connection information so you don't have to remember "magic numbers" for each client/database mapping, and can easily update port-numbers/hostnames, cluster-members as necessary. The same connection with Redis::Directory would look like this: require "redis_directory" cache = Redis::Directory.new("redis.example").connect("cache", "acme")