选择一个Scala Web框架 [英] Choosing a Scala web framework

问题描述

我要为应该在Tomcat服务器上运行的Web应用程序启动一个项目.我决定去Scala(我工作的另一种选择是Groovy)，本质上是为了确保类型安全.现在，我面临着为工作选择合适工具的任务.

I am about to start a project for a web application that should run on a Tomcat server. I have decided to go for Scala - the other alternative where I work being Groovy - essentially for type safety. I am now faced with the task of choosing the right tools for the job.

我将需要开发的项目只能通过JSON API访问.它将与自己的数据库以及两个外部服务进行交互，这两个服务分别公开JSON和XML API.我还需要能够安排定期的作业，其中我的应用程序将使用这些外部服务执行各种同步任务.

The project I will need to develop will be accessed only through a JSON API. It will interact both with its own database and with two external services, which expose respectively a JSON and XML API. I will also need to be able to schedule periodic jobs where my application will execute various synchronization tasks with these external services.

对于数据库，我希望能够在Scala中定义我的模型并自动生成模式.如果需要更改我的模型，我希望进行迁移以处理它.

For the database, I would like to be able to define my models in Scala and automatically generate the schema. If the need arises to change my models, I would like to have migrations to handle it.

对于此应用程序，我正在尝试评估提升，游戏"！ 2和Scalatra.

For this application, I am trying to evaluate Lift, Play! 2 and Scalatra.

• 升降是我的首选.它是这三个项目中最成熟的项目，并且似乎被认为是高度安全的(我不想在安全性方面做出妥协).此外，它具有Scala中似乎是最好的JSON处理库的功能.不过，经过一番尝试之后，我不确定这是否是正确的选择.该文档并不是我所见过的最好的文档.而且，在我看来，Record + Squeryl似乎比Mapper更好，但有关此用途的文档更加匮乏.最后，尽管Lift当然可以用于创建Web服务，但它的真正优势似乎在于状态处理，因此我不认为我的项目需要额外的复杂性.

• Lift was my first choice. It is the most mature of the three projects, and seems to be considered highly secure (I do not want to compromise on security). Moreover it features what seems to be the best JSON handling library in Scala. Still, after dabbling a bit with it, I am not sure this would be the right choice. The documentation is not exactly the best I have seen. Moreover, Record + Squeryl seems to me a better abstraction than Mapper, but documentation for this use is even more scarce. Finally, although Lift can certainly be used to create a web service, it seems that its real strength lies in the state handling, and so I am not convinced that the additional complexity is needed for my project.

播放！ 2 似乎有更好的文档，对我来说似乎更熟悉(我来自Django背景).同样，它的默认数据库抽象并不能真正使我满意:ANORM依赖于SQL，这对类型检查没有帮助.无论如何，我都将不得不使用Squeryl，而且我不确定该用例的文档是否还不错.此外，部署Play！目前，有2个应用程序比我想要的要复杂.一个必须安装Play！在生产服务器上，我不确定这是我工作的选项.否则，有一个插件可以使其与servlet容器一起使用，但是它是一个非常新的东西，我不确定它的稳定性/可靠性.

Play! 2 seems to have a better documentation, and looks more familiar to me (I come from a Django background). Again, its default database abstraction does not really appease me: ANORM relies on SQL, which does not help with type checking. I would have to use Squeryl anyway, and I am not sure whether the documentation for this use case is as good. Moreover, deploying Play! 2 applications is at the moment moer complicated than I'd like. One has to install Play! on the production server, and I am not sure this is an option where I work. Otherwise, there is a plugin to to make it work with servlets containers, but it is very new and I am not sure how stable/reliable it is.

最后，可以选择使用 Scalatra . Scalatra似乎很容易设置，并且它完全是为创建Web服务而设计的.折衷方案是Scalatra没有提供太多功能.它不与现有的ORM集成，也不建议如何组织应用程序的模型部分，并且对设计cron或命令行任务没有帮助.我也不确定该项目的长期前景.

Finally there is the option of using Scalatra. Scalatra seems very easy to set up, and it is designed exactly to create web services. The compromise is that Scalatra does not offer much functionality. It does not integrate with existing ORMs or suggest how to organize the model part of the application, and it does not help in designing cron or command line tasks. I am also not sure about the long term future of the project.

您认为什么是我完成任务的最佳选择?

What do you think would be the best choice for my task?

推荐答案

如果您来自MVC背景，那么Play将是您最熟悉的背景. Lift不是MVC，需要花费一些时间才能将其包裹住.

If you are coming from a MVC background then Play will feel the most familiar. Lift is not MVC and it takes some time to wrap your head around it.

没有理由不能将Scala与基于Java的框架(例如Jersey，Spring MVC， Dropwizard)一起使用，Restlet，RESTEasy等.或者您可以将Scala与Grails一起使用，就像可以将Java与Grails一起使用一样.注-Groovy从2.0版开始具有类型安全性，因此需要考虑这一点.

There is no reason that you can't use Scala with a Java-based framework like Jersey, Spring MVC, Dropwizard, Restlet, RESTEasy, etc. Or you could use Scala with Grails just like you can use Java with Grails. Note - Groovy has type safety starting with version 2.0 so that's something to consider.

如果您正在考虑Scalatra，请不要忘记 Spray ，未过滤，

If you are thinking about Scalatra then don't forget Spray, Unfiltered, BlueEyes...

请务必查看Matt Raible的网络的全面比较框架.还有其他一些SO问题: 用于Rest API服务器的Scala框架?，

Be sure to check out Matt Raible's comprehensive comparison of web frameworks. And these other SO questions: Scala framework for a Rest API Server?, How to implement a REST Web Service using Akka?

这篇关于选择一个Scala Web框架的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！