Mysql compatible proxy to Elasticsearch, Mongo, Google Datastore backend sources, including join.
Make data more accessible and usable by querying data existing datasources using mysql protocol.
This proxy translates from mysql to backend protocol (elasticsearch, mongo, etc) by implementing a full
relational algebra layer to run sql queries and poly-fill missing features. So, a
backend key-value storage such as redis can now have aggregate functions, where etc.
- Distributed Distributed from the start, run queries across multiple servers
- Hackable DataSources Very easy to add a new DataSource for your custom data, files, json, csv, storage.
- Hackable Functions Add custom go functions to extend the sql language.
- Joins Get join functionality between heterogeneous sources.
- Frontends currently only MySql protocol is supported but Postgres, CQL, Memcached, etc are planned.
- Backends Elasticsearch, Google-Datastore, Mongo currently implemented.
| Mongo | SQL Query |
|---|---|
show collections |
show tables; |
| na, -- runtime inspection | describe mytable; |
db.accounts.find({},{created:{"$gte":"1/1/2016"}}).count(); |
select count(*) from accounts WHERE created > "1/1/2016"; |
db.article.find({"year":{"$in": [2013,2014,2015] }},{}} |
select * from article WHERE year IN (2015,2014,2013); |
db.article.find({"created":{"$gte": new Date('Aug 01, 2011'), "$lte": new Date('Aug 03, 2013') },{title:1,count:1,author:1}} |
`SELECT title, count, author FROM article WHERE created BETWEEN todate("2011-08-01") AND todate("2013-08-03") |
db.article.find({"title":{"Pattern":"^list","Options":"i"}},{title:1,count:1}) |
SELECT title, count AS ct FROM article WHERE title like \"list%\" |
| na, not avail in mongo (polyfill in dataux) | SELECT avg(CHAR_LENGTH(CAST(title, \"AS\", \"CHAR\"))) AS title_avg FROM article; |
| need to document ... | select min(year), max(year), avg(year), sum(year) from table WHERE exists(a); |
| ES API | SQL Query |
|---|---|
| Aliases | show tables; |
| Mapping | describe mytable; |
| hits.total for filter | select count(*) from table WHERE exists(a); |
| aggs min, max, avg, sum | select min(year), max(year), avg(year), sum(year) from table WHERE exists(a); |
| filter: terms | select * from table WHERE year IN (2015,2014,2013); |
| filter: gte, range | select * from table WHERE year BETWEEN 2012 AND 2014 |
- Backends: Redis, CSV, Json-Files, Kafka, Rest api's
- Pub-Sub for Writes
Hacking
- see tools/importgithub for tool to import 2 days of github data for examples above.
# to run queries below, run test data import
go get -u github.com/dataux/dataux
cd $GOPATH/src/github.com/dataux/dataux/tools/importgithub
go build
./importgithub ## will import ~200k plus docs from Github archive
- Data-Accessability Making it easier to query, access, share, and use data. Protocol shifting (for accessibility). Sharing/Replication between db types.
- Scalability/Sharding Implement sharding, connection sharing
| Name | Scaling | Ease Of Access (sql, etc) | Comments |
|---|---|---|---|
| Vitess | Y | for scaling (sharding), very mature | |
| twemproxy | Y | for scaling memcache | |
| Couchbase N1QL | Y | Y | sql interface to couchbase k/v (and full-text-index) |
| prestodb | Y | query front end to multiple backends, distributed | |
| cratedb | Y | Y | all-in-one db, not a proxy, sql to es |
| codis | Y | for scaling redis | |
| MariaDB MaxScale | Y | for scaling mysql/mariadb (sharding) mature | |
| Netflix Dynomite | Y | not really sql, just multi-store k/v | |
| redishappy | Y | for scaling redis, haproxy | |
| mixer | Y | simple mysql sharding |
We use more and more databases, flatfiles, message queues, etc. For db's the primary reader/writer is fine but secondary readers such as investigating ad-hoc issues means we might be accessing and learning many different query languages.
Credit to mixer, derived mysql connection pieces from it (which was forked from vitess).
In Internet architectures, data systems are typically categorized into source-of-truth systems that serve as primary stores for the user-generated writes, and derived data stores or indexes which serve reads and other complex queries. The data in these secondary stores is often derived from the primary data through custom transformations, sometimes involving complex processing driven by business logic. Similarly data in caching tiers is derived from reads against the primary data store, but needs to get invalidated or refreshed when the primary data gets mutated. A fundamental requirement emerging from these kinds of data architectures is the need to reliably capture, flow and process primary data changes.
from Databus