azavea / grout-2018-fellowship

This is a (possibly temporary) issue-tracking repo for the Grout fellowship in 2018; there's not anticipated to be much if any code here

2 stars 1 forks source link

Evaluate NoSQL backends and providers #35

Closed jeancochrane closed 6 years ago

jeancochrane commented 6 years ago

Overview

This PR adds my research evaluating NoSQL backends and providers for Grout.

Notes

Best viewed on GitHub.
While this document takes the form of an ADR for simplicity, it doesn't recommend an immediate decision. After weighing the pros and cons, I'm undecided as to whether we should prioritize this work. As such, I'm presenting the ADR not to propose a firm decision, but rather to disseminate information to help us plan for the next sprint.

CloudNiner commented 6 years ago

Nice research. A bit late, but the Urban Apps team is doing work storing/querying GeoJSON in AWS DynamoDB using java bindings and AWS SAM for the Treetective project. If you're interested in that, it could be worth talking to @maurizi, who's the project lead.

flibbertigibbet commented 6 years ago

As I'm involved in both Treetective and with this project, I brought this overlap up early on @CloudNiner and that has partially informed the discussion of DynamoDB as an option here.

jeancochrane commented 6 years ago

Thanks for the comment @CloudNiner! I didn't know that Urban Apps had been doing some related work with DynamoDB. Given your experience @flibbertigibbet, is there anything in the DynamoDB section that seems inaccurate?

flibbertigibbet commented 6 years ago

We had discussed this in some meetings @jeancochrane, and I'd brought this up with @maurizi, so no, I don't have any further input on this section now. I'd looked at it when it was authored, but not posted a review. Good summary.