npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

eriksen

v1.3.3

Published

A model-marshalling library for dual-write/single-read data migrations

Downloads

12

Readme

Eriksen

Build Status

Eriksen is a model factory that makes it easy to write model code that retrieves or saves data to multiple, configurable places. It's main job is to Marshal reads & writes to a configurable and swappable backend, allowing for a separation that preserves an interface even when the backend data storage system changes.

Installation

npm i eriksen

Why?

Eriksen is useful when you're writing code that may change database backends, or if you're currently changing code to move from one backend to another. Since it concerns itself with only the db interactions from your code, it allows your data access code to be more modularized within a codebase. And since Eriksen acts as the coding interface, you should not need to change any other code unless expectations change as db backends switch in or out.

Because Eriksen sits between the code that accesses a backend storage system, this allows for Eriksen to log failures for a non-primary backend in the background.

Usage

This example creates two models in different databases and configures eriksen to use cassandra as the primary and dynamodb as the secondary. It calls the getAllOfTheThings method with cassandra as the primary, meaning if the getAllOfTheThings fails in dynamo, it just logs out the errors, does not fail the call. If the primary fails it will throw an error.

  // cassandra model
  const cassandraMapper = {
    getAllOfTheThings: (name) => {
      return cassandra.query("SELECT ...");
    }
  }

  // dynamo model
  const dynamoMapper = {
    getAllOfTheThings: (name) => {
      return aws.dynamodb.DocumentClient(...);
    }
  }

  const Eriksen = require('eriksen');
  const model = new Eriksen('allThings');
  model.addModel('cassandra', cassandraMapper);
  model.addModel('dynamodb', dynamoMapper);
  model.configure({
    primary: cassandraMapper,
    secondary: dynamoMapper
  });

  function retrieveAllOfTheThings(thingName) {
    return model.proxy.getAllOfTheThings(name);
  }

  // calling function that calls the eriksen instance to marshall calls
  retrieveAllOfTheThings('allMyThings')
    .then((things) => {
      console.log('list of my things', things);
    })
    .catch((err) => {
      console.log(`it failed ${err.message}`);
    });