3 ms·

Backend: Scala Spark - http://sparkjava.com http://sparkjava.com ScalikeJDBC - http://scalikejdbc.org http://scalikejdbc.org Postgres Coming from Rubyland

Backend: Scala Spark - http://sparkjava.com http://sparkjava.com ScalikeJDBC - http://scalikejdbc.org http://scalikejdbc.org Postgres Coming from Rubyland (and AR specifically), I despise writing a bunch of dao/repo code, so I've resorted to codegen-ing my daos/repos. Frontend: Aurelia - http://aurelia.io http://aurelia.io

thinkdevcode 11y ago
I also highly recommend Aurelia. It's a fantastic and future proof front-end library. Out of curiosity, why Spark over Scalatra? (http://scalatra.org/ http://scalatra.org/)
- davidkellis 11y ago
  I used Scalatra on one other project, and I found it to be difficult to deploy. Whether it's true or not, my impression is that Spark is a little simpler to use and deploy than Scalatra. Scalatra is my second choice though.
- fokinsean 11y ago
  What makes you say it is future proof?
  - jethro_tell 11y ago
    I assume he's been to the future, that's the only way one could know.
  - thinkdevcode 11y ago
    By future-proof I didn't actually mean forever. It heavily makes use of es6/es7, so it was designed with "forward-thinking" design choices (forward thinking is what I intended when I wrote future proof). Right now it relies on babel, but as es6/es7 gains adoption it'll grow out of requiring it. Similar to Angular 2.0, which is also being developed with a forward thinking mindset.
jacques_chester 11y ago
> I despise writing a bunch of dao/repo code, so I've resorted to codegen-ing my daos/repos. Spring Data does this very well, in a fashion partly inspired by ActiveRecord. You define a Repository interface with whatever search methods suit your case; a concrete class is built and injected for you. The same interface can back onto JPA databases, Mongo, Redis and I forget what else. If you add Spring Data REST, you get a complete RESTful API -- complete with HATEOAS, paging, sorting, searching and HAL -- automagically. Use Spring Boot and you won't need to do any more than include the dependencies in your Maven POM or build.gradle file.

thinkdevcode 11y ago

I also highly recommend Aurelia. It's a fantastic and future proof front-end library. Out of curiosity, why Spark over Scalatra? (http://scalatra.org/ http://scalatra.org/)

davidkellis 11y ago
I used Scalatra on one other project, and I found it to be difficult to deploy. Whether it's true or not, my impression is that Spark is a little simpler to use and deploy than Scalatra. Scalatra is my second choice though.
fokinsean 11y ago
What makes you say it is future proof?
- jethro_tell 11y ago
  I assume he's been to the future, that's the only way one could know.
- thinkdevcode 11y ago
  By future-proof I didn't actually mean forever. It heavily makes use of es6/es7, so it was designed with "forward-thinking" design choices (forward thinking is what I intended when I wrote future proof). Right now it relies on babel, but as es6/es7 gains adoption it'll grow out of requiring it. Similar to Angular 2.0, which is also being developed with a forward thinking mindset.

jacques_chester 11y ago

> I despise writing a bunch of dao/repo code, so I've resorted to codegen-ing my daos/repos. Spring Data does this very well, in a fashion partly inspired by ActiveRecord. You define a Repository interface with whatever search methods suit your case; a concrete class is built and injected for you. The same interface can back onto JPA databases, Mongo, Redis and I forget what else. If you add Spring Data REST, you get a complete RESTful API -- complete with HATEOAS, paging, sorting, searching and HAL -- automagically. Use Spring Boot and you won't need to do any more than include the dependencies in your Maven POM or build.gradle file.