Pondering 2.1 to 3.0

54 views
Skip to first unread message

Richard Rodseth

unread,
Apr 29, 2015, 8:05:14 PM4/29/15
to scala...@googlegroups.com
Congrats on the release of 3.0!

I have an Akka/Spray/Slick app. The other night I switched Slick versions (in a branch) and if I remember rightly the package change was the only source change I needed to make.

Is it fair to say that it's pretty safe to upgrade, and then incrementally introduce
- use of new config and default pool
- use of new APIs and database closing
?

Does the Database closing go in a shutdown hook? 
Any performance improvements *without* using the new APIs?

I currently have a routed DbActor (no asks, just tells and response messages) and BoneCp config. 








Reply all
Reply to author
Forward
0 new messages