CODEWITHSUNDEEP
scalaplayframeworkslickplay-slick
Driver
Driver

Reputation: 548

Play Framework and Slick project architecture

I'm migrating an Application from Grails to Play Framework and i'm currently trying to figure out what's the best way of organizing the project structure.

I want to use Slick Codegen alongside with Flyway for Migrations, cause i want to keep a track of all the migrations that are being done (a solution similar to Rails Migrations would be perfect).

I see that Play Framework has the Play-Slick module but from what i've noticed, everything just happens like pure black-magic.

I saw an example on GitHub where Slick Modelling, Play Framework and Flyway Migrations are 3 separate SBT Modules, which makes perfect sense in case we ever want to move away from Play Framework.

Now, my questions is: What's the best architecture approach for a Play Framework App?

Note: I'm a newbie in Play Framework and Scala.

Upvotes: 0

Views: 729

Answers (1)

pedrorijo91
pedrorijo91

Reputation: 7865

I did a post a while ago about using Play + slick + mysql. Is has the minimal structure to work, but the one I found more correct (I think this point will be subjective): http://pedrorijo.com/blog/play-slick/

or the source code at https://github.com/pedrorijo91/play-slick3-steps

Upvotes: 1

Related Questions