Hubs is a rapidly scalable data gateway platform.
Build data-rich applications without building backend APIs and boilerplate code for basic CRUD operations to your favorite database and/or third party APIs.
Teams spend countless hours writing repetitive code to fetch and put data to a variety of backend data sources. The majority of data connections in modern times connect via a handful of protocols, leaving developers largely copying and pasting mostly verbatim code to simply get and put data for their applications.
With Hubs, we've abstracted the repetitive boilerplating, freeing developers to connect the world's most popular SQL databases and any HTTP Rest API in seconds within the same interface you test adhoc queries and connections via Nokori UI.
Hubs organizes logically grouped data souces/connections in to data "Hubs" that allow developers to organize connections not by database or api endpoint, but by related kind/type for ease of access and rapid development.
Compose SQL queries directly in the UI, test them, then deploy them as consumable REST endpoints that can be consumed by any application or service.
Once connected, developers can consume all connected data sources globally via a univerally consistent, singular REST API endpoint via SDK or API.
The goal is rapid development and deployment of new applications via ease of data access.
We have an exciting list of features planned for Hubs, including:
- MySQL Support
- Postgres Support
- MariaDB Support
- HTTP Rest API Support
- SQL Query Composing & Testing
- One-Click REST Endpoint Deployment
- ๐ง Triggers [WIP]
- ๐ง Webhooks
- Data Enrichers
- Event Subscriptions
- Data Pipelines
- Write Throughput Multipliers
- Query Analytics
- Query Caching
- Query Rate Limiting
- Respone Transformers
- Multi-Source Real-Time Materialized Views
Feature request? Open an issue to get the convo started.
Hubs is accessible via REST API or SDK.
To get started, init a new project, configure basic project settings, and the build script will generate your API Key that can be used for API Requests, SDK, and to enable Nokori UI to connect with your Hubs instance.
npm i
npm run init
Save your API key at the end of the process and include it in API requests using the header X-Nokori-API
if not using the SDK or UI.
npm run dev
To consume data once endpoints are saved/deployed is as easy as:
import nokori from '@nokori/js-sdk'
const nk = nokori('api_key')
const { data, error } = await nk.query.execute({
queryId: 'nk.q.-ddqHfqeZNihbChcAbf', //Global Cloud Query ID
context: {
name: formData.get('name'),
},
})
curl https://api.nokori.com/v1/queries/execute \
-X POST
-H 'x-nokori-api-key: {{apiKey}}' \
-H 'Content-Type: application/json' \
-d '{"queryId": "nk.q.Yum6RAQFvj2eMf5kLKR", "context": {}}'
Full documentation coming soon...
There is a deployment actions file in the .github/workflows
folder that serves as a good base for deploying to AWS. Assumes you are running ubuntu >18.04 on EC2.