Displaying 1 to 20 from 283 results

gh-ost - GitHub's Online Schema Migrations for MySQL

  •    Go

gh-ost is a triggerless online schema migration solution for MySQL. It is testable and provides pausability, dynamic control/reconfiguration, auditing, and many operational perks.gh-ost produces a light workload on the master throughout the migration, decoupled from the existing workload on the migrated table.

orchestrator - MySQL replication topology management and HA

  •    Go

orchestrator actively crawls through your topologies and maps them. It reads basic MySQL info such as replication status and configuration.It provides with slick visualization of your topologies, including replication problems, even in the face of failures.

kingshard - A high-performance MySQL proxy

  •    Go

kingshard is a high-performance proxy for MySQL powered by Go. Just like other mysql proxies, you can use it to split the read/write sqls. Now it supports basic SQL statements (select, insert, update, replace, delete). The most important feature is the sharding function. Kingshard aims to simplify the sharding solution of MySQL. The Performance of kingshard is about 80% compared to connecting to MySQL directly.kingshard is under the Apache 2.0 license. See the LICENSE directory for details.

mysql - Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package

  •    Go

Make sure Git is installed on your machine and in your system's PATH.Go MySQL Driver is an implementation of Go's database/sql/driver interface. You only need to import the driver and can use the full database/sql API then.




PyMySQL - Pure Python MySQL Client

  •    Python

This package contains a pure-Python MySQL client library. The goal of PyMySQL is to be a drop-in replacement for MySQLdb and work on CPython, PyPy and IronPython.NOTE: PyMySQL doesn't support low level APIs _mysql provides like data_seek, store_result, and use_result. You should use high level APIs defined in PEP 249. But some APIs like autocommit and ping are supported because PEP 249 doesn't cover their usecase.

db - Productive data access layer for Go.

  •    Go

The upper.io/db.v3 package for Go is a productive data access layer for Go that provides a common interface to work with different data sources such as PostgreSQL, MySQL, SQLite, MSSQL, QL and MongoDB.Take the tour to see real live examples in your browser.


mycli - A Terminal Client for MySQL with AutoCompletion and Syntax Highlighting

  •    Python

MyCLI is a command line interface for MySQL, MariaDB, and Percona with auto-completion and syntax highlighting.

flipper - :dolphin: feature flipping for ruby (performant and simple)

  •    Ruby

Feature flipping is the act of enabling or disabling features or parts of your application, ideally without re-deploying or changing anything in your code base. The goal of this gem is to make turning features on or off so easy that everyone does it. Whatever your data store, throughput, or experience, feature flipping should be easy and have minimal impact on your application.

python-mysql-replication - Pure Python Implementation of MySQL replication protocol build on top of PyMYSQL

  •    Python

Pure Python Implementation of MySQL replication protocol build on top of PyMYSQL. This allow you to receive event like insert, update, delete with their datas and raw SQL queries. The project is used in production for critical stuff in some medium internet corporations. But all use case as not been perfectly test in the real world.

dolibarr - Dolibarr ERP CRM is a modern software package to manage your company or foundation activity (contacts, suppliers, invoices, orders, stocks, agenda,

  •    PHP

Dolibarr ERP & CRM is a modern software package to manage your organization's activity (contacts, suppliers, invoices, orders, stocks, agenda…). It's an Open Source Software (written in PHP language) designed for small, medium or large companies, foundations and freelances.

mysql_utils - Pinterest MySQL Management Tools

  •    Python

It is hoped that this code will be useful to you as an example of working implementations of DB tools. MySQL servers at Pinterest are launched, live, and die with only the rarest of configuration changes. Upgrading kernels, MySQL versions, and any other changes that would require a restart of the database are never done in-place. Instead, these actions are always performed through server replacements and failovers/slave promotions as needed. This choice has greatly simplified our automation by removing the need to manage intermediate state.

onebody - private member portal for churches, built with Ruby on Rails

  •    Ruby

OneBody is open-source, web-based social networking, email list, online directory, and lightweight document management software for churches. This software has been in production use at churches for over ten years. Every feature is built by actual church members to meet the need of their own church.

vitess - Vitess is a database clustering system for horizontal scaling of MySQL.

  •    Go

Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. By encapsulating shard-routing logic, Vitess allows application code and database queries to remain agnostic to the distribution of data onto multiple shards. With Vitess, you can even split and merge shards as your needs grow, with an atomic cutover step that takes only a few seconds.

sqler - write APIs using direct SQL queries with no hassle, let's rethink about SQL

  •    Go

SQL-er is a tiny portable server enables you to write APIs using SQL query to be executed when anyone hits it, also it enables you to define validation rules so you can validate the request body/query params, as well as data transformation using simple javascript syntax. sqler uses nginx style configuration language (HCL) amd javascript engine for custom expressions. RESTful server could be used to interact directly with i.e mobile, browser, ... etc, in this mode SQLer is protected by authorizers, which gives you the ability to check authorization against another 3rd-party api. Each macro you add to the configuration file(s) you can access to it by issuing a http request to /<macro-name>, every query param and json body will be passed to the macro .Input.