Our motivation was to create a message broker for microservices, with the simplest connection possible.
We pay special attention to the environments from which you can access the network: IS Network works not only on server, but also in browser tabs, mobile applications, applications on the router.
IS Network is an api-oriented virtual network. For identification in the network IS Keys are used. To provide access to resources, the concept of contracts is used.
npm install --save @inshel/node
import Node from '@inshel/node'
const connect = async () => {
const node = new Node()
await node.connect()
}
-
InShel Node
Node supports your connection with InShel Network. -
Keys
InShel network use RSA keys to authorize nodes.
Your can manage your keys in explorer.inshel.dev -
Invites
InShel Network has closed beta status.
We use invites to provide access. -
Contracts
Contracts solve routing problem in InShel Network.
Your can manage your contracts in explorer.inshel.dev -
Contract keys
Contract keys allow your clients use InShel Network.
This keys can execute strict only its contracts lambda and can't work with other contracts and invites. -
Rays
Ray is a contracts event bus. -
Redirect
IS Network allow redirect lambda execution.
Create environment
mkdir ./environment
touch ./environment/key
touch ./environment/node-key
To start tests your must have valid keys with invites.
- fix docs
- readme.md
- docs/contracts.md
- docs/keys.md
- docs/rays.md
First implementation
- node
- keys
- invites
- contracts
- contract-keys
- rays