joepie91
/
dlayer
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
A GraphQL-like data access layer
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10 Commits
1 Branch
0 Tags
110 KiB
JavaScript 100%
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3e0c1b6b56'
${ noResults }
Go to file
Sven Slootweg 3e0c1b6b56 Add todo 12 months ago
misc Remove outdated comment 12 months ago
.gitignore Initial commit 1 year ago
README.md Initial commit 1 year ago
cursor.js Initial commit 1 year ago
deep-merge-and-map.js Ensure that methods in a module's root schema also receive a module-bound context 1 year ago
docs.md Initial commit 1 year ago
index.js Add todo 12 months ago
load-modules.js Patch type methods with module context 12 months ago
notes.txt Initial commit 1 year ago
package.json 0.1.3 12 months ago
test.js Initial commit 1 year ago
yarn.lock Initial commit 1 year ago

README.md

dlayer

This library (and its documentation) is still a work-in-progress!

dlayer is a GraphQL-like data access layer. It lets you combine data from multiple sources into a single coherent API - and it's designed for application-internal use first and foremost, with network accessibility being an optional add-on.

dlayer differs from GraphQL in a number of important ways:

  • dlayer supports recursive queries without needing schema hacks; both bounded and unbounded.
  • dlayer is modular by default; a dlayer API can be composed of many independent 'modules' that can reference and extend each other when available. This allows for eg. constructing plugin systems, like in sysquery, as well as making it easier to loosely couple your API definition.
  • dlayer does not use a separate schema; the schema is implicitly defined by what the API returns. This essentially makes it dynamically typed; however, trying to access a non-existent property of the schema is an error.