Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DynamoDB, PostgreSQL, and Grout #27

Open
gassc opened this issue Sep 5, 2018 · 0 comments
Open

DynamoDB, PostgreSQL, and Grout #27

gassc opened this issue Sep 5, 2018 · 0 comments

Comments

@gassc
Copy link
Member

gassc commented Sep 5, 2018

I've currently got the FishFry data in DynamoDB. With that, the fishfryform web app's GUI forms and ReST API are carrying the burden of schema validation and gate-keeping for the database. While within the code base a thin "database interface layer" keeps the Dynamo-specific code at arms-length from everything else, everything still sort of bends towards accommodating unstructured data. Having the app need to enforce schema sort of cancels out the benefits of using a schema-less database; either I maintain schema enforcement logic in the app or the database does it natively. It's been a fun experiment.

It would be nice to get back to using a normal PostgreSQL database so we can do more fun spatial things with PostGIS, but maintain the schema flexibility inherent in something like DynamoDB. So...

...if there's time early in 2019, I might swap out DynamoDB for a hosted PostgreSQL database and use Grout, which is a relatively new thing from Azavea.

We'll see!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant