Loopback: AWS DynamoDB Connector ?

[docoder]

I want to use AWS DynamoDB, so how I will get AWS DynamoDB Connector ?

[raymondfeng]

Do you want to give https://github.com/tmpaul/jugglingdb-dynamodb a try? I'm not the developer, but it probably requires minimal effort to get it working with LB.

[PerfectedApp]

@docoder raymondfeng is right. Anything JugglingDB should be compatible or near compatible.

[marcellodesales]

Has anyone tried this?

https://github.com/claylo/loopback-connector-dynamodb

We decided to use StrongLoop, but without DynamoDB we can't go to EC2

[simonguest]

Looking through the repo (https://github.com/claylo/loopback-connector-dynamodb), it appears to be an early/partial implementation. Supports creating objects, but no other methods at this time.

[dpurrington]

@raymondfeng can you explain what you mean by "give it a try?" Is it possible just to plug in the jugglingdb-dynamodb package directly? If so, I can't find the info I need to try that. Or does the code need to be ported to the loopback-connector-dynamodb package?

[alemhnan]

Any news on this or hints on this? They both (https://github.com/claylo/loopback-connector-dynamodb and https://github.com/claylo/loopback-connector-dynamodb) are not actively maintaned.
There are npm library actively maintained (https://github.com/victorquinn/dynasty, https://github.com/totemstech/node-dynamodb), could a connector be built based on that?

[ahmed-abdulmoniem]

Any news on that guys?

[aggied]

Bump. Taking a cursory look at Loopback for potential use in an upcoming project, but the lack of a dynamoDB connector is causing me to take a pause.

[demsey2]

any update on this one

[aaronjhoffman]

Also interested in this, has anyone found a solution?

[demsey2]

can anyone from IBM confirm if there is a plan to include that

[fizzl]

Seeing how IBM is integrating LoopBack into their Bluemix Api Connect solution, it seems unlikely that they are interested in DynamoDB integration.

So, I guess we are waiting for some individual to do it.

[pbrain19]

Ok guys looks like we will just have to use the one originally mentioned on top. According to the details I see it appears to be working.

[emtiazahmed]

Any progress on this? I want to go with loopback but without this connector it would be impossible.

[superkhau]

We do not have any current plans to support the connector on the roadmap.

Would any of you guys like to make a community connector? We could add it to strongloop-community like https://github.com/strongloop-community/loopback-connector-elastic-search (which is actively maintained by one of our community members @pulkitsinghal).

cc @bajtos

[mandarzope]

I have created loopback-connector-dynamodb

Its was forked from juggling-dynamo it is still in under progress.

We are using it in our production. It currently does not support String and Number sets. Support will be added in few days.
If someone wants to try it out then please try.
I am sure you will find few bugs.

Thanks.
Mandar

[bajtos]

@mandarzope this is awesome! Would you mind adding a mention of your project to our "Community projects" section on loopback.io, see http://loopback.io/doc/en/community/How-to-add-a-project.html. Possibly to "Community connectors" section in https://loopback.io/doc/en/lb2/Community-connectors.html too.

@crandmck I think there is a bit of overlap between those two doc pages, is it perhaps worth either unifying them, or at least adding a link from "Community projects" to "Community connectors"?

I am closing this issue as done.

[crandmck]

there is a bit of overlap between those two doc pages, is it perhaps worth either unifying them, or at least adding a link from "Community projects" to "Community connectors"?

I don't see any overlap, unless I'm misunderstanding. "How to add a project" gives instructions on how to add a project to the LoopBack community section in the docs, while "Community connectors" is just a list of some of the data source connectors developed by the LB community.

But adding a link from "Community projects" to "Community connectors" makes sense, so I'll do that.

[crandmck]

Added by https://github.com/strongloop/loopback.io/commit/1115f425c0f8af9d78173f4552050773a722af7c

[bajtos]

@crandmck thank you for adding the link, should we perhaps add it to the sidebar too?

Sorry for not being clear in my comment. What I meant is that the sidebar on http://loopback.io/doc/en/community/index.html lists a single community-maintained connector "Elasticsearch connector", which seems a bit random to me. What is the criteria used to decide which community connectors should be listed in the sidebar?

[crandmck]

Oh, I see.

Yes, you are correct that the community projects listed are fairly random. When I created the site, I just picked a few prominent ones. Frankly, I don't recall the rationale for adding the Elasticsearch connector.

In general, the idea of this part of the site is to provide a place for open-source projects to promote themselves, so it's up to the project contributors to add their page as described in http://loopback.io/doc/en/community/How-to-add-a-project.html. The ones I added are just examples. I suppose I should post on the GG to get more people to add their projects...

Anyway.... I could certainly duplicate http://loopback.io/doc/en/lb3/Community-connectors.html in the "community" area, but that not really a "project page" but rather a list of (some) connectors aimed more at someone who just wants to use them rather than as a promotion of the projects.

If you nevertheless think that would be worthwhile to include there, I don't have a big objection. LMK.

[bajtos]

On the second though, I think the current status is good enough, let's focus our energy on improving other things.

[SippieCup]

@mandarzope How do you query a table that has both hash & sort key attributes by just the hash key using your connector in loopback.

I keep getting a PKMissingError for the model if I do not include a sort key.

[levantoanbkit]

We are a small startup team, we are excited about LoopBack + DynamoDB to run on the AWS Elastic Beanstalk. @mandarzope Do you have a plan for distribution your loopback-connecter-dynamodb to popular developer? Can you share something about the detail information in README.md?
Thank you so much!

[SippieCup]

@levantoanbkit

You might want to consider looking at my fork of the dynamodb connector at @UnisonoInc/loopback-connector-dynamodb. Unlike mamdarzope's, It has full composite key support to take advantage of dybamodbs performance benefits and is about ready for production.

[mandarzope]

@SippieCup
thanks for developing dynamodb connector. Unfortunately we couldn't develop it further.

@levantoanbkit
From our experience with dynamodb, we choose to use DocumentClient from aws-sdk. It gave us better flexibility to execute dynamo queries. It's convenient and safe to use if there is no future migration from dynamodb to other database.

[levantoanbkit]

Thank you @SippieCup and @mandarzope so much! We will try to use your connectors and improve it when we detected a bug.

[SippieCup]

Hi @levantoanbkit,

It won't be hard to find bugs as mine is not fully production ready at this time, please
list any issues you find and I'll get them fixed or just send me a pull
request.

You will also need to import loopback-dynamo-model and use that as a base class rather than persisted Model. Feel free to reach out to me on Gitter.im (I'm in the strongloop channel). It might be a pain to set up without any documentation to do so.

@mandarzope: would you mind allowing me to take over the npm entry for
loopback-connector-dynamodb for my connector at this time?

On Apr 30, 2017 9:59 AM, "Toan Le" [e-mail] wrote:

Thank you @SippieCup https://github.com/SippieCup and @mandarzope
https://github.com/mandarzope so much! We will try to use your
connectors and improve it when we detect a bug.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/strongloop/loopback/issues/1033#issuecomment-298234010,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApdj3OM-olJLkOWX4loCh-45rgRTHCEks5r1JPSgaJpZM4DVHsU
.

[mandarzope]

@SippieCup
Sure. You can take up loopback-connector-dynamodb

[SippieCup]

@mandarzope,

Great to hear, thanks. When possible, please add my npm account - andrewsidhu - as an owner to the NPM package.

npm owner add andrewsidhu loopback-connector-dynamodb

Thanks once again for providing the framework for me to get started on it.

[duongNA]

@SippieCup
Your repository seems more complicated to mandarzope's repo.
There are a lot of new files and classes.
Does we have unit tests for those files and new functions?

[SippieCup]

@duongNA

I have backported the test cases from our private repo to the public connector repo.

Keep in mind sharding still has a few issues when generating the table programatically, However if you generate the tables in dynamodb's CLI or on AWS console it works fine.

I will put together a readme for others to be able to easily adopt the new DAO and be able to use the DynamoDB connector.

Once again, it is not 100% ready for production but is in a position that it can easily be brought to that point.

The new files and functions are actually forked from Loopback juggler's DAO object and updated to support composite keys like dynamo has.

[eduar2]

Is there any recent works on this?

[johndpope]

@eduar2 - https://github.com/letsfullstack/loopback-connector-dynamodb

[SippieCup]

That's awesome to see!