Adopt `sbt-dynamodb` into the Scanamo organisation?

[rtyley]

Adopt `sbt-dynamodb` into the Scanamo organisation?

[kailuowang]

I am not against it. I migrated away from sbt-dynamodb (to using docker) for all my own projects a while ago. That is to say I myself don't have a personal incentive for maintaining it.

I can't speak too much for scanamo development, for application development, docker was more transparent and flexible for me. Another factor is that when I have multiple external application dependencies, it's much nicer to have an unified mechanism to manage their runtime in docker compose than ad hoc solutions like sbt-dynamodb for each one.

[rtyley]

I migrated away from sbt-dynamodb (to using docker) for all my own projects a while ago.

That's interesting! Do you have an example of configuring an sbt project that way - I assume this is using the Docker version of AWS's DynamoDB Local?

[kailuowang]

That's interesting! Do you have an example of configuring an sbt project that way - I assume this is using the Docker version of AWS's DynamoDB Local?

You can find it in https://github.com/iheartradio/thomas/
I set it up in a way so that I can have two local environments: one for integration tests, in which all data are transient (wiped clean every time tests are run), and one with persistent data for a mimic of prod runtime locally. I named them "test" and "dev". They use different ports and data volumes so that tests don't accidentally wipe out dev runtime data. Here is the setup

• A very simple Docker file based off local dynamo with persistent data

• standard docker compose file with env

• env file for "dev"

• env file for "test"

• facility code in buid.sbt (for run docker in sbt)

  • actually runn docker
  • tasks defs here, here and here
  • some sbt alias to help switch between dev and test

• one last thing is make sure that your test code and application code use different port to access dynamo.

Hope that helps but feel free to ask if you have any questions.