awesome-repositories.com
Blog
awesome-repositories.com

Découvrez les meilleurs dépôts open-source grâce à notre recherche par IA.

ExplorerRecherches sélectionnéesAlternatives open sourceLogiciels auto-hébergésBlogPlan du site
ProjetÀ proposNotre méthodologiePresseServeur MCP
Mentions légalesConfidentialitéConditions d'utilisation
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

3 dépôts

Awesome GitHub RepositoriesDatabase Host Distribution

Strategies for distributing connection requests across multiple database server hosts.

Distinguishing note: None of the candidates cover server-side host distribution or load balancing for database connections.

Explore 3 awesome GitHub repositories matching data & databases · Database Host Distribution. Refine with filters or upvote what's useful.

Awesome Database Host Distribution GitHub Repositories

Trouvez les meilleurs dépôts grâce à l'IA.Nous recherchons les dépôts les plus pertinents grâce à l'IA.
  • mysqljs/mysqlAvatar de mysqljs

    mysqljs/mysql

    18,623Voir sur GitHub↗

    This project is a MySQL database driver and client for Node.js. It provides a JavaScript implementation of the MySQL protocol to facilitate connecting to, querying, and managing data within MySQL databases. The driver includes a connection pool manager to maintain a cache of reusable database connections, reducing the overhead of frequent network handshakes. It also supports row-by-row result streaming to process large datasets without loading entire result sets into memory. Core capabilities cover SQL query execution, the management of database transactions, and the coordination of multiple

    Distributes connection requests across multiple database hosts using strategies like Round-Robin or Random.

    JavaScriptjavascriptmysqlnodejs
    Voir sur GitHub↗18,623
  • crunchydata/postgres-operatorAvatar de CrunchyData

    CrunchyData/postgres-operator

    4,423Voir sur GitHub↗

    This project is a Kubernetes operator designed for deploying and managing production PostgreSQL database clusters using declarative configurations. It functions as a controller that synchronizes the actual state of database clusters with a desired state, providing a system for high availability orchestration, automated backup and recovery, and containerized database administration. The operator distinguishes itself through a comprehensive data protection suite that supports point-in-time recovery, multi-mode backups to cloud object storage, and cluster cloning. It ensures continuous availabil

    Cloud-Native Backup Archiving uses affinity and topology constraints to prevent multiple database pods from landing on the same host.

    Go
    Voir sur GitHub↗4,423
  • garden-co/jazzAvatar de garden-co

    garden-co/jazz

    2,537Voir sur GitHub↗

    Jazz is a local-first relational database and synchronization framework designed for offline-capable applications. It functions as a reactive state management system that treats database records as the primary source of truth, automatically updating user interfaces in real time as underlying data changes. The project distinguishes itself through a collaborative data synchronization model that utilizes row-level versioning to track branching edit histories. It implements a security engine based on identity-claim row security, which enforces granular permissions on individual records, and suppo

    Spreads data across a fault-tolerant cloud system that scales resources based on actual usage.

    TypeScriptcrdtcrdtsdatabase
    Voir sur GitHub↗2,537
  1. Home
  2. Data & Databases
  3. Database Host Distribution

Explorer les sous-tags

  • Geo-Optimized HostingDistributing data across a fault-tolerant cloud system optimized for geographic proximity. **Distinct from Database Host Distribution:** Focuses on geo-optimized distributed hosting and auto-scaling rather than just connection load balancing.
  • Pod Anti-Affinity ConstraintsConfiguration rules that prevent multiple database instances from being scheduled on the same physical host or zone. **Distinct from Database Host Distribution:** Focuses on physical pod placement and fault tolerance, whereas Database Host Distribution usually refers to traffic/connection routing.