Orchestrate.io JavaScript Client Library

Today I’m starting a project working with Orchestrate.io’s API & open source software collaborations. More about the project in a moment, let’s get up to speed on what I’ll be including in this project. My main focus is to build a client library to access Orchestrate.io. During building this I’ll dive into the key value, graph and other storage mechanisms that the client library will provide. Beyond that, I’ll take a stroll through building an NPM library and the pertinent JavaScript the library. So buckle up, we’re going on a code slinging hash writing hacking session.

Over the course of putting together this material, I’ll be posting most of the core material on Orchestrate.io’s blog, so subscribe for updates as they come out. Feedly is a good option, connect via searching for “orchestrate.io” or navigate over to the Orchestrate.io blog itself. ;)

Project Effort Context

During building the client I’ll take a dive into who, what, where, when, why and how to interact with the various data structures. I’ll aim for the client to follow the model of the existing Go Client Library that is available at Orchestrate Go Client on Github. It follows a basic model as shown below in Go language.

    c := client.NewClient("Your API Key")
    // Get a value
    value, _ := c.Get("collection", "key")
    // Put a value
    c.Put("collection", "key", strings.NewReader("Some JSON"))
    // Search
    results, _ := c.Search("collection", "A Lucene Query")
    // Get Events
    events, _ := c.GetEvents("collection", "key", "kind")
    // Put Event
    c.PutEvent("collection", "key", "kind", strings.NewReader("Some JSON"))
    // Get Relations
    relations, _ := c.GetRelations("collection", "key", []string{"kind", "kind"})
    // Put Relation
    c.PutRelation("sourceCollection", "sourceKey", "kind", "sinkCollection", "sinkKey")

I’ll be working on this client, but don’t hold back on me, feel free to jump in with some of your own code or telling me I wrote some code wrong or whatever. I’d gladly accept any committers jumping in to help out. The more we all work together the more useful information I can provide during this project.

Once this project has produced a workable client pending interest from the community I’ll put together some material about where, how and some best uses around using the client in your Node.js Application. Even prospectively build a JavaScript client side library prospectively for use with Angular or other popular client side libraries.

References

6 thoughts on “Orchestrate.io JavaScript Client Library

    • btw – thank’s for the reference to Steve’s project w/ Bowery. It’s come in super handy over the last X months, and gave me the ability to pivot the symphonize project into something else! :)

  1. Orchestrate.io, Webstorm, Hacking Some Code and Project Pivots | Composite Code

  2. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library | Composite Code

  3. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library : CloudAve

  4. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library – Composite Code

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s