blocks|key|299961|text|我将推荐Unfiltered。这是一个惯用的Web框架，它以“Scala的方式”来处理事情，而且非常漂亮。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|299962|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/unfiltered/Unfiltered^0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm going to recommend <a href="https://github.com/unfiltered/Unfiltered" rel="noreferrer">Unfiltered</a>. It's an idiomatic Web framework that does things "the Scala way" and is very beautiful.

blocks|key|294891|text|我会再添加两个选项:具有内置JAX-RS支持的akka和简单地直接使用JAX-RS+(可能是Jersey实现)。虽然可以说"Scala-y“比其他方法更少(依赖于注释来绑定参数和路径)，但JAX-RS使用起来很愉快，以最小的占用空间干净利落地解决了web服务编码的所有问题。我没有通过akka使用它，我期望它在那里非常出色，通过它基于延续的实现获得令人印象深刻的可扩展性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|294892|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would add two more options: akka with built-in JAX-RS support, and simply using JAX-RS directly (probably the Jersey implementation). While arguably less "Scala-y" than others (relying upon annotations to bind parameters and paths), JAX-RS is a joy to use, cleanly solving all of the problems of web service coding with minimal footprint. I've not used it via akka, I would anticipate it being excellent there, getting impressive scalability via it's continuation-based implementation.

blocks|key|299973|text|没有特定的顺序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|299974|299975|Akka+HTTP|unordered-list-item|offset|length|299976|Spray+|299977|DropWizard|299978|REST.li|299979|http4s|299980|Blue+Eyes|299981|Finagle+/+Lift+JSON-一种容错的、与协议无关的RPC+|299982|+squbs+(article)+(tutorial)+RPC+system+|299983|Play!++and+Play-mini!+/Lift+JSON--简化了REST服务的提供。|299984|299985|entityMap|0|LINK|mutability|MUTABLE|url|http://doc.akka.io/docs/akka-http/current/scala.html|1|http://spray.io/|2|https://dropwizard.github.io/dropwizard/|3|https://github.com/linkedin/rest.li/wiki/Scala-Integration|4|http://http4s.org/|5|https://github.com/jdegoes/blueeyes|6|https://github.com/twitter/finagle|7|https://github.com/paypal/squbs|8|http://www.josephpconley.com/2014/03/04/building-better-apis-with-play.html|9|http://nordicapis.com/building-a-rest-api-in-java-scala-using-play-framework-2-part-1/|10|http://www.playframework.org/^0|0|0|0|9|0|0|0|5|1|0|0|A|2|0|0|7|3|0|0|6|4|0|0|9|5|0|0|7|6|0|1|5|7|8|7|8|I|8|9|0|0|L|A|0|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1S|8|@]|9|@$F|1T|G|1U|1|1V]]|A|$]]|$1|H|3|I|5|E|7|1W|8|@]|9|@$F|1X|G|1Y|1|1Z]]|A|$]]|$1|J|3|K|5|E|7|20|8|@]|9|@$F|21|G|22|1|23]]|A|$]]|$1|L|3|M|5|E|7|24|8|@]|9|@$F|25|G|26|1|27]]|A|$]]|$1|N|3|O|5|E|7|28|8|@]|9|@$F|29|G|2A|1|2B]]|A|$]]|$1|P|3|Q|5|E|7|2C|8|@]|9|@$F|2D|G|2E|1|2F]]|A|$]]|$1|R|3|S|5|E|7|2G|8|@]|9|@$F|2H|G|2I|1|2J]]|A|$]]|$1|T|3|U|5|E|7|2K|8|@]|9|@$F|2L|G|2M|1|2N]|$F|2O|G|2P|1|2Q]|$F|2R|G|2S|1|2T]]|A|$]]|$1|V|3|W|5|E|7|2U|8|@]|9|@$F|2V|G|2W|1|2X]]|A|$]]|$1|X|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]|18|$5|11|12|13|A|$14|19]]|1A|$5|11|12|13|A|$14|1B]]|1C|$5|11|12|13|A|$14|1D]]|1E|$5|11|12|13|A|$14|1F]]|1G|$5|11|12|13|A|$14|1H]]|1I|$5|11|12|13|A|$14|1J]]|1K|$5|11|12|13|A|$14|1L]]|1M|$5|11|12|13|A|$14|1N]]|1O|$5|11|12|13|A|$14|1P]]]]

In no particular order: 

<ul>
<li><a href="http://doc.akka.io/docs/akka-http/current/scala.html" rel="noreferrer">Akka HTTP</a></li>
<li><a href="http://spray.io" rel="noreferrer">Spray</a> </li>
<li>Paypal <a href="https://github.com/paypal/squbs" rel="noreferrer">squbs</a> (Akka/Spray) </li>
<li><a href="https://dropwizard.github.io/dropwizard/" rel="noreferrer">DropWizard</a></li>
<li><a href="https://github.com/linkedin/rest.li/wiki/Scala-Integration" rel="noreferrer">REST.li</a></li>
<li><a href="http://http4s.org/" rel="noreferrer">http4s</a></li>
<li><a href="https://github.com/jdegoes/blueeyes" rel="noreferrer">Blue Eyes</a></li>
<li><a href="https://github.com/twitter/finagle" rel="noreferrer">Finagle</a> - A fault tolerant, protocol-agnostic RPC system </li>
<li><a href="http://www.playframework.org/" rel="noreferrer">Play! and Play-mini!</a> (<a href="http://www.josephpconley.com/2014/03/04/building-better-apis-with-play.html" rel="noreferrer">article</a>) (<a href="http://nordicapis.com/building-a-rest-api-in-java-scala-using-play-framework-2-part-1/" rel="noreferrer">tutorial</a>) </li>
<li><a href="http://www.assembla.com/wiki/show/liftweb/REST_Web_Services" rel="noreferrer">Lift</a> / Lift JSON.- makes it simple to provide REST services. </li>
</ul>

blocks|key|3023066|text|到目前为止都是不错的答案。Lift的优点之一是它的RestHelper，它可以非常容易地编写简短、优雅的API方法。此外，您想要做的所有其他事情在Lift中的实现都应该相当简单。也就是说，Memcache可能不是必需的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3023067|entityMap|0|LINK|mutability|MUTABLE|url|http://www.assembla.com/wiki/show/liftweb/REST_Web_Services^0|P|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

All good answers so far. One point in Lift's favor is its <a href="http://www.assembla.com/wiki/show/liftweb/REST_Web_Services" rel="nofollow noreferrer">RestHelper</a>, which can make it quite easy to write short, elegant API methods. In addition, all the other things you want to do should be quite straight-forward to implement in Lift. That being said, Memcache might be not be necessary.

blocks|key|3023108|text|看看Xitrum+(我是它的作者)，它提供了您列出的所有内容。Its+doc是相当广泛的。来自自述文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3023109|Xitrum是一个基于Netty和Hazelcast的异步群集Scala+web框架和web服务器：|3023110|在JAX-RS的精神中，|3023111|注释用于|unordered-list-item|3023112|路由。你不必在一个地方声明所有的路由。在Netty.|3023113|Sessions的精神下，|3023114|Async可以存储在cookies或集群cookies和集群缓存中，你不需要单独的缓存servers.|3023115|In-process和集群|3023116|，你不需要单独的Comet服务器。|3023117|3023118|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ngocdaothanh/xitrum|1|https://xitrum-framework.github.io/^0|2|6|0|V|7|1|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]|$A|19|B|1A|1|1B]]|C|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1D|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1E|8|@]|9|@]|C|$]]|$1|K|3|L|5|J|7|1F|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|1G|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1H|8|@]|9|@]|C|$]]|$1|Q|3|R|5|J|7|1I|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1J|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]]]

Take a look at <a href="https://github.com/ngocdaothanh/xitrum" rel="nofollow noreferrer">Xitrum</a> (I'm its author), it provides everything you listed. <a href="https://xitrum-framework.github.io/" rel="nofollow noreferrer">Its doc</a> is quite extensive. From README:

Xitrum is an async and clustered Scala web framework and web server on top of Netty and Hazelcast:

<ul>
<li>Annotation is used for URL routes, in the spirit of JAX-RS. You don't have to declare all routes in a single place.</li>
<li>Async, in the spirit of Netty.</li>
<li>Sessions can be stored in cookies or clustered Hazelcast.</li>
<li>In-process and clustered cache, you don't need separate cache servers.</li>
<li>In-process and clustered Comet, you don't need a separate Comet server.</li>
</ul>

blocks|key|3237491|text|虽然有点晚，但我绝对推荐使用Bowler框架来创建REST+API，它很小，而且支持自动case类转换！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3237492|entityMap|0|LINK|mutability|MUTABLE|url|http://bowlerframework.org/^0|E|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

A little late on the scene but I would definitely recommend using <a href="http://bowlerframework.org/" rel="nofollow">Bowler</a> framework for creation of REST API's. It small, to the point and automatic case class conversion support!

blocks|key|297446|text|看看Finch，这是一个用于构建Finagle+HTTP服务的Scala+combinator库。Finch允许您从大量预定义的基本块中构造复杂的HTTP端点。与解析器组合子类似，Finch端点很容易重用、组合、测试和推理。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|297447|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/finagle/finch|1|https://twitter.github.io/finagle/^0|2|5|0|G|7|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Take a look at <a href="https://github.com/finagle/finch" rel="nofollow noreferrer">Finch</a>, a Scala combinator library for building <a href="https://twitter.github.io/finagle/" rel="nofollow noreferrer">Finagle</a> HTTP services. Finch allows you to construct complex HTTP endpoints out of the number of predefined basic blocks. Similarly to parser combinators, Finch endpoints are easy to reuse, compose, test, and reason about.

We are thinking on moving our Rest API Server (it is inside the web service, on Symfony PHP) to Scala for several reasons: speed, no overhead, less CPU, less code, scalability, etc. I didn't know Scala until several days ago but I've been enjoying what I've been learning these days with the Scala book and all the blog posts and questions (it's not so ugly!)

I have the following options:

<ul>
<li>build the Rest API Server from scratch</li>
<li>use a tiny Scala web framework like <a href="http://github.com/scalatra/scalatra" rel="noreferrer">Scalatra</a></li>
<li>use Lift</li>
</ul>

Some things that I will have to use: HTTP requests, JSON output, MySQL (data), OAuth, Memcache (cache), Logs, File uploads, Stats (maybe Redis).

What would you recommend?

Scala framework for a Rest API Server?

服务器

路由

MySQL

Redis

OAuth

JSON

我们正在考虑将我们的Rest API Server (它在web服务中，在Symfony PHP上)迁移到Scala，原因有几个:速度快，没有开销，CPU更少，代码更少，可伸缩性，等等。我直到几天前才知道Scala，但我一直很享受这些天来我通过Scala这本书和所有的博客帖子和问题所学到的东西(它并不是那么丑陋！)我有...

问Rest API服务器的Scala框架？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rest API服务器的Scala框架？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rest API服务器的Scala框架？
EN