I'll feedback what I can when I can. Evaluating all the current frameworks for use in our new technology
stack is a big job. Particularly when you need to consider more than just best-of-breed and functionality,
but also maturity vs. bleeding edge, future enhancement, and support.
Data persistence is only one aspect as we also need to re-evaluate UI frameworks, security, and so on.
What we currently have is very good but starting to show its age now.
Overall what we're looking for in frameworks is support of easy to write and maintain application code. Not
too concerned if integrating the frameworks is complex provided that it is largely transparent to the
In the case of persistence framework, a clean interface with the business object model is probably the
major requirement with database portability high on the list as well. So something like Slick is nice
but still leaves the need for a layer (ala ORM) to integrate cleanly with the business object layer.
Hibernate is nice because of its maturity but becoming legacy in the new technology stack particularly
given that Scala is almost certainly going to be our language of choice. We haven't used Hibernate
previously so legacy support isn't really necessary.
Activate was looking good but the whole STM thing seemed to add complexity due to functionality that
we probably won't need.
While researching Activate I came across mapperdao which then looked like being everything we needed;
sans the DDL generation. Still appears to be the front-runner.
However, all my comments so far are only based on project documentation and what I have been able to
learn from public discussions. Hoping to get stuck into some concrete POC development in the next few
weeks. Will keep you in the loop with findings / questions re mapperdao as we go.