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

loopback-connector-neptune

v0.0.3

Published

Loopback 4 connector for AWS Neptune using Gremlin Graph Query Language.

Downloads

2

Readme

Loopback 4 Connector for AWS Neptune (BETA)

Loopback 4 connector for AWS Neptune using Gremlin Graph Query Language.

This connector has the intent of connecting Loopback to AWS Neptune and use the Loopback ORM language to facilitate the use of basic operations like Create, Update and Delete. It also allows the use of audit layers and middlewares when using CRUD methods.

This connector allows you to run direct queries (raw queries) using Gremlin bytecode format with Graph Traversal Steps. It doesn't support Gremlin script execution in order to avoid injections.

It uses non-authenticated connection and IAM authentication method. You can also use this to connect to other Gremlin based GraphDB's, but it wasn't tested, so, be careful. The code used for IAM authentication was based on Lambda Example from AWS Neptune documentation.

It does support Neptune "transactions", which is called Multithreaded Gremlin Writes and runs internally in Neptune engine, it's NOT the standard Gremlin transaction, please read Neptune documentation to understand what it means.

Installing

npm install loopback-connector-neptune

Gremlin Client Version

The Gremlin Client Version is important for Neptune compatibility as you can read at Neptune engine version Docs. We're using Gremlin ^3.4.12.

Setup

Please read and follow each step of setup because all parameters must be present to have the connector working properly with GraphDB Neptune.

Debugging

DEBUG=loopback:connector:neptune npm start

Tests

You can find all tests and code examples at Loopback Neptune Connector Test Kit Repository which has a Docker environment to run functional tests using Apache TinkerPop. Note that Apache TinkerPop doesn't have the exactly same behavior of AWS Neptune, there are some limitations you must validate running the tests against a real Neptune instance. Please follow the instructions on Test Kit Repository of how to do that.

License

This connector is under MIT license which means, you can modify and distribute since your code is OpenSource and free for use by anyone.

Contributions

There are so many other tests to be created and issues to be fixed especially when new Neptune versions are released. Create a fork, do your improvements with well done comments and documentation if needed, create a pull request, and the community will be eternally grateful for your help ;)