blocks|key|296623|text|这与previous+question相关，如果不是完全相同的话！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|296624|这不是一个简单的问题，因为并发的执行元模型允许构建许多不同类型的应用程序，从有状态的单VM应用程序(具有几个单独的执行元类)到由数千个执行元类实例组成的无状态集群。|style|BOLD|296625|然而，核心原则是相同的：|296626|296627|永远不会仅通过传递不可变的消息|unordered-list-item|296628|来公开参与者的消息|296629|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1549251/scala-actors-worst-practices^0|2|H|0|0|G|5|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@$A|12|B|13|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|16|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|17|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

<p>This is related to a <a href="https://stackoverflow.com/questions/1549251/scala-actors-worst-practices">previous question</a>, if not <em>exactly</em> the same! </p>

<p>It's not such a simple question because the <strong>actor model</strong> of concurrency allows for many different types of applications to be built, from a stateful single-VM application (with a few separate actor classes) to a stateless cluster of thousands of instances of an actor class. </p>

<p>The core principles are the same however:</p>

<ul>
<li>Never expose an actor's state</li>
<li>Communicate solely via the passing of immutable messages</li>
</ul>


blocks|key|294747|text|几周前，我在Scala的learnings+of+actor+development上发布了一篇博客。这是一篇基于几年的范例经验的最佳实践和应该避免的事情的帖子。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|294748|entityMap|0|LINK|mutability|MUTABLE|url|http://chariotsolutions.com/blog/post/learnings-from-actor-development/^0|C|U|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]]]]

<p>I posted a blog on <a href="http://chariotsolutions.com/blog/post/learnings-from-actor-development/" rel="nofollow noreferrer">learnings of actor development</a> in Scala a few weeks ago.  It's a post of a best practices and things to avoid based on a few years of experience with the paradigm.</p>


blocks|key|3016642|text|“反应式设计模式”这本书正在曼宁编写中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3016643|请参阅：https://www.manning.com/books/reactive-design-patterns|offset|length|3016644|entityMap|0|LINK|mutability|MUTABLE|url|https://www.manning.com/books/reactive-design-patterns^0|0|4|1I|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

<p>The book 'Reactive Design Patterns' is in the making at Manning.</p>

<p>See: <a href="https://www.manning.com/books/reactive-design-patterns" rel="nofollow">https://www.manning.com/books/reactive-design-patterns</a></p>


<p>I am struggling to find any decent links to design patterns, best practice or good, basic architectural principles that should be used in building Actor-based apps. Those few that I know of are:</p>

<h3>Blog posts, articles, WIKIs, guides</h3>

<ul>
<li><a href="http://www.erlang.org/doc/design_principles/users_guide.html" rel="noreferrer">OTP Design Principles User's Guide</a> </li>
<li><a href="http://www.eaipatterns.com/" rel="noreferrer">Patterns and Best Practices for Enterprise Integration</a> (in general, can be applied to any message-driven architecture)</li>
<li>Series of <a href="http://james-iry.blogspot.com/search/label/parallel%2Fdistributed%2Fconcurrent" rel="noreferrer">posts by James Iry on dealing with state in design with actors</a> </li>
<li>Series of <a href="http://www.tikalk.com/category/tags/scala-actors" rel="noreferrer">posts on design with Scala actors</a> by Ittay Dror</li>
<li><a href="http://en.wikipedia.org/wiki/Concurrency_pattern" rel="noreferrer">Concurrency patterns</a> article on wikipedia</li>
<li><a href="http://horicky.blogspot.com/2010/10/scalable-system-design-patterns.html" rel="noreferrer">Scalable System Design Patterns</a> (not directly related to actors, but quite useful)</li>
<li>Understanding actor concurrency, <a href="http://www.javaworld.com/javaworld/jw-02-2009/jw-02-actor-concurrency1.html" rel="noreferrer">pt.1</a>, <a href="http://www.javaworld.com/javaworld/jw-03-2009/jw-03-actor-concurrency2.html" rel="noreferrer">pt.2</a> by Alex Miller</li>
</ul>

<h3>Papers</h3>

<ul>
<li><a href="http://erlang.org/download/armstrong_thesis_2003.pdf" rel="noreferrer">Disseration on making reliable distributed systems</a> by Joe Armstrong</li>
<li><a href="http://lampwww.epfl.ch/~odersky/papers/ScalableComponent.html" rel="noreferrer">Scalabale Component Abstractions</a> by Philipp Haller and Martin Odersky</li>
<li><a href="http://lampwww.epfl.ch/~odersky/papers/jmlc06.html" rel="noreferrer">Event-based programming without inversion of control</a> by Martin Odersky and Matthias Zenger</li>
<li><a href="http://ww2.cs.mu.oz.au/~sulzmann/talks/coordination08-talk.pdf" rel="noreferrer">Actors with Multi-Headed Message Receive Patterns</a> by Martin Sulzmann</li>
</ul>

<h3>Books</h3>

<ul>
<li><a href="http://www.artima.com/shop/actors_in_scala" rel="noreferrer">Actors In Scala</a> by Philipp Haller and Frank Sommers</li>
<li><a href="http://pragprog.com/titles/jaerlang/programming-erlang" rel="noreferrer">Programming Erlang</a> by Joe Armstrong</li>
<li><a href="http://www.manning.com/logan/" rel="noreferrer">Erlang and OTP in Action</a> by Martin Logan, Eric Merritt, and Richard Carlsson</li>
</ul>

<h3>Implementations</h3>

<ul>
<li><a href="http://doc.akkasource.org/" rel="noreferrer">Akka Framework</a> (alternative implementation of actors in Scala with a port of several Erlang behaviors and lots of other relized patterns for actors)</li>
<li><a href="http://docs.google.com/present/view?id=ddmk3f43_63zpg3jcgz" rel="noreferrer">Scalaz Actors</a> (actor compositions, strategies and promises)</li>
</ul>

<h3>Presentations</h3>

<ul>
<li><a href="http://www.infoq.com/presentations/Actor-Thinking" rel="noreferrer">Actor Thinking</a> by Dale Schumacher </li>
<li><a href="http://www.infoq.com/presentations/1000-Year-old-Design-Patterns" rel="noreferrer">1000 Year-old Design Patterns</a> by Ulf Wiger</li>
<li><a href="http://www.infoq.com/presentations/Actor-based-Programming" rel="noreferrer">Actor-based Programming</a> by Jamie Ridgway</li>
<li><a href="http://www.slideshare.net/remeniuk/ss-8206699" rel="noreferrer">Школа Актерского Мастерства</a> by Vasil Remeniuk</li>
</ul>

<h3>Examples from highscalability.com</h3>

<ul>
<li><strong><a href="http://highscalability.com/build-infinitely-scalable-infrastructure-100-using-amazon-services" rel="noreferrer">Simple queuing service (SQS)</a></strong> - this service provides an internet scale queuing service for storing messages. Distributed actors put work on the queue and take work off the queue. Typical use: a centralized work queue. You put jobs on the queue and different actors can pop work of the queue and process them when they get CPU time. Part of scalability. Have any number of producers and consumers. You don't worry about it. Queues are spread across multiple machines and multiple data centers.</li>
</ul>


Design patterns/best practice for building Actor-based system

数据中心

Erlang

我正在努力寻找到设计模式、最佳实践或良好的基本架构原则的任何像样的链接，这些原则应该用于构建基于Actor的应用程序。我所知道的为数不多的是：博客文章、文章、维基、指南  (通常，可以应用于Ittay Dror在wikipedia上的文章中所写的任何message-driven architecture)Series ...

问构建基于角色的系统的设计模式/最佳实践
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问构建基于角色的系统的设计模式/最佳实践EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问构建基于角色的系统的设计模式/最佳实践
EN