Ifrit
Getting started
Installation
npm install ifrit
Usage
const Ifrit = require("../dist")
const mongodb = require("mongodb")
const schema = require("./schema.json")
const query = `
SELECT name, details.biographical.class AS class, details.biographical.age AS age
WHERE NOT(bad_guy) AND details.physical.gender = "male"
ORDER BY details.biographical.age
LIMIT 2
`
mongodb.MongoClient
.connect("mongodb://localhost:27017/ifrit")
.then((db) => {
return db
.collection("mages")
.aggregate(Ifrit.compile.mongodb(schema, query))
.toArray()
})
.then(console.log)
.catch(console.err)
Documentation
Ifrit is available as a Node.js module as well as a PureScript module. The JavaScript
documentation is accessible on github pages. A
documentation for PureScript is published on
pursuit.
Examples
Different scenarios are available on the repository in the examples
folder. Here's a
summary of all examples:
schema
schema
{
"name": "string",
"bad_guy": "boolean",
"details": {
"biographical": {
"age": "number",
"class": "string"
},
"physical": {
"gender": "string",
"height": "number"
}
},
"spells": [{
"name": "string",
"power": "number"
}]
}
Bad guys' names
example 001
SELECT name
WHERE bad_guy = true
Minimal age of female mages
example 002
SELECT name, MIN(details.biographical.age) AS min_age
WHERE details.physical.gender = "female"
GROUP BY NULL
Average power for mages under 170cm, by class
example 003
SELECT AVG(spells_power) AS power
FROM (
SELECT AVG(spells.power), details.biographical.class AS class
WHERE details.physical.height < 170
)
GROUP BY class
Names and classes of the first two good guys, ordered by age
example 004
SELECT name, details.biographical.class AS class, details.biographical.age AS age
WHERE NOT(bad_guy) AND details.physical.gender = "male"
ORDER BY details.biographical.age
LIMIT 2
Names and average size of the first three females order by height
example 005
SELECT name, AVG(details.physical.height)
WHERE details.physical.gender = "female"
GROUP BY NULL
ORDER BY details.physical.height
LIMIT 3
Overview
What & Why ?
Ifrit is a compiler from SQL to NoSQL for data aggregation. NoSQL databases are great at
modelling structured, unstructured and polymorphic data and usually offer powerful map-reduce
based API when it comes to data aggregation. However, it is truly challenging to leverage those
API in a web service.
In a nutshell, Ifrit:
- Offers aggegation capabilities to any API via a neat and well-known syntax
- Ensures the semantic correctness of a request
- Embraces security concerns by clearly defining the scope of each request
- Produces an easy-to-use output, without any dependencies or pre-requisite setup
- Has a small fingerprint on your integration and performances
How it works
Ifrit builds an Abstract Syntax Tree (AST) which represents only syntactycally correct
requests. Then, it generates a request corresponding to a specific driver. So far, MongoDB is
the only target driver available.
_ __
\ /
\ +----------+ +-----------+ +----------+ +----------+ /
SQL = =| tokenize +---------> parse +--------> verify +--------> generate |= = NoSQL
/ +----------+ +-----------+ +----------+ +----------+ \
_/ \__
Example (MongoDB)
input
SELECT COUNT(_id) AS nb_txs WHERE amount > 1000 GROUP BY account.currency
output
[
{
"$match": {
"amount": {
"$gt": 1000
}
}
},
{
"$group": {
"_id": "$account.currency",
"nb_txs": {
"$sum": 1
}
}
}
]
Schema definition
Ifrit acts on a single collection at a time and does not support joins. Therefore, a schema is
required in order to verify the request (semantically and security wise). Schemas are defined
as JSON objects in a declarative syntaxe.
Ifrit supports the following primitive types: number
, string
, boolean
and null
. Arrays
and objects can be declared by nesting primitive types in JSON arrays []
or objects {}
.
Ifrit can only see what's defined in a schema. The compilation will fail if the request tries
to use or select a field not present in the schema. This can be used to control the scope of
what elements are accessible via the query.
Example:
{
"amount": "number",
"account": {
"country": "string",
"currency": "string"
},
"items": [{
"price": "number",
"description": "string"
}]
}
SQL language support
type | support |
---|
projection | SELECT, AS, FROM |
grouping | GROUP BY |
filtering | WHERE, LIMIT, OFFSET |
sorting | ORDER BY, DESC, ASC |
operators | AND, OR, NOT, =, !=, >, < |
function | applicable type |
---|
AVG | number |
COUNT | any |
MAX | number |
MIN | number |
SUM | number |
⚠ Ifrit relies on a strict order of clauses ⚠
- (1)
SELECT
- (2)
FROM
- (3)
WHERE
- (4)
GROUP BY
- (5)
ORDER BY
- (6)
(ASC | DESC)
- (7)
LIMIT
- (8)
OFFSET
Differences with SQL
-
Ifrit is case-sensitive, e.g. AS != as
, NULL != null
, etc.
-
Ifrit doesn't support the *
selector.
-
ORDER BY
can't be use with NULL
.
-
Ifrit can't JOIN
from other collections, the FROM
can only be used to defined derived
tables, i.e, define a multi-level pipeline of map / reduce operations.
-
Aggregation functions can be applied to numbers when used with GROUP BY
or directly to
array of numbers when apply without. Ifrit also supports nested notation for array of objects
(e.g. SELECT AVG(items.price)
).
-
When no alias is specified, the property of the output schema is named after the selector.
(with MongoDB, .
in names are replaced with _
).
Benchmark
On a classic i7 quad-core, 16Gb DDR5 RAM / Ubuntu 16.04
SELECT age
> 9,795 ops/sec ±0.40% (91 runs sampled)
SELECT class AS klass, COUNT(bonus)
> 4,791 ops/sec ±0.83% (90 runs sampled)
SELECT AVG(age) GROUP BY class
> 5,754 ops/sec ±0.58% (94 runs sampled)
SELECT is_master WHERE age > 14 AND age < 20
> 4,586 ops/sec ±0.65% (93 runs sampled)
SELECT AVG(power) AS avg_pow FROM (SELECT AVG(spells.power), age) WHERE age > 18 GROUP BY NULL
> 2,378 ops/sec ±0.63% (93 runs sampled)
Changelog
Roadmap
- Support for
*
joker in select - Augment support for binary & unary operators
- Augment support for projections & aggregations functions
- Support basic arithmetic in projections & aggregations
2017-04-02 | 0.1.0
-
Support for the following keyword:
SELECT
FROM
WHERE
GROUP BY
ORDER BY
(ASC | DESC)
LIMIT
OFFSET
-
Support for the following boolean operators:
-
Support for the following binary operators:
-
Support for the following unary operators:
-
Support for the following functions (projections & aggregations):
-
Support for aliases inside SELECT
-
Support for nested objects
-
Support for derived tables
Compatibility
Credits