良好的用例阿卡 [英] Good use case for Akka

查看:165
本文介绍了良好的用例阿卡的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我听说过许多热烈讨论阿卡框架(Java /斯卡拉服务平台),但到目前为止,还没有看到使用的很多实际例子情况下,它是很好的。所以,我有兴趣听到有关的事情开发商已成功使用过它。

I have heard lots of raving about Akka framework (Java/Scala service platform), but so far have not seen many actual examples of use cases it would be good for. So I would be interested in hearing about things developers have used it succesfully.

只有一个限制:请不要写包括聊天服务器的情况。 :-)
(为什么?因为这已经被过度使用作为范例来大量的类似的东西)

Only one limitation: please do not include case of writing a chat server. :-) (why? since this has been overused as an example for lots of similar things)

修改:由于有许多很好的答案,我的选择接受的答案是有点任意的;我以为最高投票人似乎是一个合理的选择。谢谢大家对好答案!

EDIT: Since there are many good answers, my choice of accepted answer is bit arbitrary; I thought highest voted one seems like a reasonable choice. Thank you everyone for good answers!

推荐答案

到目前为止,在两个真正的项目非常成功的我已经用它。两者在近实时交通信息领域(交通在高速公路上的车),分布在多个节点,几方,可靠的后端系统之间的整合消息。我不能随意给客户端上的细节然而,当我得到确定,也许它可以被添加作为参考。

I have used it so far in two real projects very successfully. both are in the near real-time traffic information field (traffic as in cars on highways), distributed over several nodes, integrating messages between several parties, reliable backend systems. I'm not at liberty to give specifics on clients yet, when I do get the OK maybe it can be added as a reference.

阿卡确实通过这些项目拉动,即使我们开始的时候它是在0.7版本。 (我们使用Scala的方式)

Akka has really pulled through on those projects, even though we started when it was on version 0.7. (we are using scala by the way)

其中的一大优点是,你可以组成一个系统出来的演员和消息几乎没有boilerplating的易用性,它扩展非常良好,无手挽线程的所有复杂,你会得到异步消息的对象之间传递的几乎免费的。

One of the big advantages is the ease at which you can compose a system out of actors and messages with almost no boilerplating, it scales extremely well without all the complexities of hand-rolled threading and you get asynchronous message passing between objects almost for free.

这是在模拟任何类型的异步消息处理的非常好。我想preFER写任何类型的(网络)服务体系的这种风格比任何其他的风格。 (你有没有试过写一个异步Web服务(服务器端)与JAX-WS?这是很多水暖)。所以,我要说,不希望在它的组件之一挂起,因为一切都在使用同步方法隐式调用任何系统,以及一个组件锁定的东西。这是非常稳定,让-IT-崩溃+监控解决方案,失败真的效果很好。一切都是易于安装和编程并不难单元测试。

It is very good in modeling any type of asynchronous message handling. I would prefer to write any type of (web) services system in this style than any other style. (Have you ever tried to write an asynchronous web service (server side) with JAX-WS? that's a lot of plumbing). So I would say any system that does not want to hang on one of its components because everything is implicitly called using synchronous methods, and that one component is locking on something. It is very stable and the let-it-crash + supervisor solution to failure really works well. Everything is easy to setup programmatically and not hard to unit test.

还有一些优秀的附加模块。
骆驼模块插头确实在早已进入阿卡并允许与配置的端点异步服务,例如简单的开发。

Then there are the excellent add-on modules. The Camel module really plugs in well into Akka and enables such easy development of asynchronous services with configurable endpoints.

我很高兴与框架,并正在成为我们构建连接系统的一个事实上的标准。

I'm very happy with the framework and it is becoming a defacto standard for the connected systems that we build.

这篇关于良好的用例阿卡的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆