Hey everyone! I'm happy to provide another update on behalf of the Standard Library team. The big news this week is that we released a solution for use as a persistence layer inside of Standard Library APIs. Simple key-value storage that's easy to set up has been one of our most requested features, and I'm excited to show it to you!

From a community standpoint, we also had the pleasure of traveling to New Jersey last weekend to help out at Hack Princeton. It was our third time at HackPrinceton, and it's always a pleasure to be able to work with such talented and driven students from all around North America. I would like to give a special shout out to the winners of our prize, TextNet and Hoot, for a couple of really creative, and well executed, projects.

Thanks again to everybody who participated, as well as Princeton and the organizers. We had a fantastic time. Now, on to product updates!

Key-Value Storage

Because all APIs built on our platform are stateless, we often get questions about configuring persistent storage for use in more complex applications. We are happy to announce that we now have an in-house solution, in the form of a simple key-value storage API. The API is available as utils.kv exposes a simple interface and is ready to use with no configuration. It's as simple as:

const kv = require('lib')({ token: process.env.STDLIB_LIBRARY_TOKEN }).utils.kv;
await kv.set({key: 'key', value: 'val'});
let results = await kv.get({key: 'key'});

All Standard Library accounts have a table automatically associated with them, tied to their username. Right now, users are restricted to a single table as we roll out the feature, but you'll have the ability to use more in the future. You can try it from the documentation page, or from Code on Standard Library (embedded below, but that link opens it in a new tab).

That's All!

As usual, thanks for reading. If you have questions or need help join our join our Slack workspace or ask us on Twitter @StandardLibrary.

Steve Meyer
Software Engineer, Standard Library