Akka v2.4.9-RC1发布,Actor 模型开发库

jopen 8年前
   <p style="text-align: center;"><img alt="" src="https://simg.open-open.com/show/7aacef690646edf9d98f9326ecb0dd6c.png" /></p>    <p>Akka 是一个用 Scala 编写的库,用于简化编写容错的、高可伸缩性的 Java 和 Scala 的 Actor 模型应用。它已经成功运用在电信行业。系统几乎不会宕机(高可用性 99.9999999 % 一年只有 31 ms 宕机)。</p>    <p>Actor模型并非什么新鲜事物,它由Carl Hewitt于上世纪70年代早期提出,目的是为了解决分布式编程中一系列的编程问题。其特点如下:</p>    <ul>     <li>系统中的所有事物都可以扮演一个Actor</li>     <li>Actor之间完全独立</li>     <li>在收到消息时Actor所采取的所有动作都是并行的,在一个方法中的动作没有明确的顺序</li>     <li>Actor由标识和当前行为描述</li>     <li>Actor可能被分成原始(primitive)和非原始(non primitive)类别</li>     <li>非原始Actor有</li>     <li>      <ul>       <li>由一个邮件地址表示的标识</li>       <li>当前行为由一组知识(acquaintances)(实例变量或本地状态)和定义Actor在收到消息时将采取的动作组成</li>      </ul> </li>     <li>消息传递是非阻塞和异步的,其机制是邮件队列(mail-queue)</li>     <li>所有消息发送都是并行的</li>    </ul>    <h2>更新日志</h2>    <ul>     <li>Overall Akka HTTP throughput and transfer rate has been improved by 30-40%</li>     <li>Performance is on-par or better than Spray.      <ul>       <li>Matching it both in raw throughput as well as latency distribution across a spectrum of request rates.</li>       <li>We measured an overall improvement of ~14% over Spray</li>      </ul> </li>     <li>Short lived connections throughput, has been <em>doubled</em>. This case remains remains the worst-case scenario for Akka HTTP, although is relatively rare in the real world (due to connection pooling),</li>     <li>Given our EC2 infrastructure (m4.2xlarge instances) the server currently reaches a maximum of ~160.000 “ping / pong” requests per second (measured using 100 concurrent connections).</li>    </ul>    <h2>下载</h2>    <ul>     <li><a href="/misc/goto?guid=4958992819459852770">Akka 2.4.9-RC1 (Scala 2.11 and Java 8+)</a></li>     <li><a href="/misc/goto?guid=4958992819582344482" rel="nofollow"><strong>Source code</strong> (zip)</a></li>     <li><a href="/misc/goto?guid=4958992819684692125" rel="nofollow"><strong>Source code</strong> (tar.gz)</a></li>    </ul>