On this page
Objective SQL on tap in highly-available, dedicated PostgreSQL instances. Get instant data APIs for your serverless app. Scale to millions.
Interact with remote data in the same object-oriented paradigm as your code.
Get auto-generated APIs (plus documentation) as you update your schema.
Take advantage of a fully managed platform to keep you focused on your app!
Think big on an enterprise-ready infrastructure! Scale up with no extra effort.
Provision a database in one click and get instant data APIs for your app! Speak the same Objective SQL as you would with a local DB. Unlock a whole new experience with an intuitive dashboard.
Watch this space for when we come in beta.
Come into the simplistic, powerful developer cloud. Save money, increase efficiency, and optimize spend with solutions that take away the process and cut the long story short.
Ride more on open source with our commitment to open source. WebQit Cloud lets you build on open technologies that you can always bank on.
Ready for a stress-free go-live experience? Watch this space for when we come in beta.
Provision a database in one click and get instant data APIs for your app! Speak the same Objective SQL as you would with a local DB. Unlock a whole new experience with an intuitive dashboard.
Watch this space for when we come in beta.
Objective SQL is a fullstack, object-oriented SQL for modern apps; one language and one API over diverse data storage technologies - from in-memory storage, to the client-side IndexedDB, to the server-side database like MySQL.
Speak the same familiar SQL language, this time, with an object-oriented convention for relationships. Or query your data programmatically using a succinct API.
Objective SQL works both in node.js and in the browser. Here's a node.js example:
// Import the inbuilt Object Storage library as the query client
import { ODB as Client } from '@webqit/objective-sql';
// Run a query
Client.query('SELECT fname, lname FROM users').then(result => {
console.log(result);
});Objective SQL is the same familiar, powerful SQL language you know…
SELECT post_title, users.fname AS author_name FROM posts
LEFT JOIN users ON users.id = posts.author_id;…but with an object-oriented syntax for relationships, built into the language…
SELECT post_title, author_id->fname AS author_name FROM posts;…and that's SQL without the query complexity!
Learn more about the language and see just what's possible with the arrow syntax. (DOCS coming soon.)
Objective SQL also lets us work programmatically using a promise-based API.
Here's the API version of the Basic Usage query we started with:
// The Client.open() method below opens the "default" database at version "0"
// More on this in the docs
Client.open().then(async DB => {
// We get a handle to the "users" store (or table)
let userStore = await DB.open('users');
// Then we run a query
let result = await userStore.getAll();
console.log(result);
});Learn more about the API and see just what's possible. (DOCS coming soon.)
Objective SQL lets us decide between underlying storage technologies without changing code.
While we've used the inbuilt in-memory store in the examples above, we could easily switch to a persistent storage engine, like the IndexedDB that ships with browsers, by simply swiping in the appropriate client in the import statement…
import {
//ODB as Client,
IDB as Client,
//SQL as Client,
} from '@webqit/objective-sql';…and the rest of the code can go on "as is".
Learn more about Storage and see just what's possible. (DOCS coming soon.)
Objective SQL completely embraces the schema idea of SQL, and offers one simple, universal way to write these schemas that describe your data - whatever the underlying storage engine.
Schema declaration is usually the first step to working with SQL. So, the users table we've used in the examples above should already have been declared. Here's how easy it is to do that:
(async () => {
const DB = await Client.create([{
name: 'users',
primaryKey: 'id',
autoIncrement: true,
fields: {id: {}, fname: {}, lname: {}, email: {}, age:{type: 'int', default:0},},
uniqueKeys: {email: 'email'},
}, {
name: 'posts',
...
}]);
// Schema created. DB ready for use...
// So we populate with data... programmatically or via queries
let userStore = await DB.open('users', 'readwrite');
userStore.addAll([
{fname: 'John', lname: 'Doe', email: 'john.doe@example.com', age: 33},
{fname: 'James', lname: 'Smith', email: 'john.doe@example.com', age: 40},
]);
})();Learn more about Schemas and see just what's possible. (DOCS coming soon.)
Web-native is an approach to web tooling that seeks to solve for the traditonal, native web over vendor-specific interests. This is an especially important goal for a web community that is now fragmented into framework silos.
WebQit Community is an initiative to support an obvious community-wide paradigm shift for web-native development. We seek to drive community participation in new ideas for the web platform, and in all the projects that are revisiting much of the assumptions that brought us here, to explore new possibilities around just conventional web languages and APIs.
We're beginning this initiative by giving mentions to the actionable discussions from around the web that are painting this future of the web. It'll be nice to see the whole picture from one place.
Come into the simplistic, powerful developer cloud. Save money, increase efficiency, and optimize spend with solutions that take away the process and cut the long story short.
Ride more on open source with our commitment to open source. WebQit Cloud lets you build on open technologies that you can always bank on.
Ready for a stress-free go-live experience? Watch this space for when we come in beta.
Web-native is an approach to web tooling that seeks to solve for the traditonal, native web over vendor-specific interests. This is an especially important goal for a web community that is now fragmented into framework silos.
WebQit Community is an initiative to support an obvious community-wide paradigm shift for web-native development. We seek to drive community participation in new ideas for the web platform, and in all the projects that are revisiting much of the assumptions that brought us here, to explore new possibilities around just conventional web languages and APIs.
We're beginning this initiative by giving mentions to the actionable discussions from around the web that are painting this future of the web. It'll be nice to see the whole picture from one place.
Taste the future today from an ecosystem of open source tooling that explores the web-native approach to engineering modern web applications. It comes bringing all of the goodness of the native web platform and the traditional paradigms that have historically been traded.
We're iterating really fast - fast going from experimental to stable - on all the new possibilities we are exploring around conventional web languages and APIs, and the traditional web.
Contributions are welcome on each project! Help report typos and bugs via github issues, or submit a fix. Contributions are taken promptly and are well-acknowledged!
Taste the future today from an ecosystem of open source tooling that explores the web-native approach to engineering modern web applications. It comes bringing all of the goodness of the native web platform and the traditional paradigms that have historically been traded.
We're iterating really fast - fast going from experimental to stable - on all the new possibilities we are exploring around conventional web languages and APIs, and the traditional web.
Contributions are welcome on each project! Help report typos and bugs via github issues, or submit a fix. Contributions are taken promptly and are well-acknowledged!