Objects, Anomalies, and Actors: The Next Revolution Steve Vinoski - PowerPoint PPT Presentation

�� interface implementation 1 1 10 9 8 7 6 �� 16 Graphics from Object-Oriented Programming with Objective C , Apple, 2011 �� 16 ��

�� Encapsulation t h e o m d m d o e h data t h t e o m d d m o e h t 17 17 ��

�� h e t o m d �� m d �� o e h data t �� h t e t h e o o m d m �� d m d d m o o e h e t h data t h �� t �� e o m d d m o e h t h e t �� o m d �� m d o e �� h data t h t �� e �� o m d �� d m o e �� h t �� 18 �� 18 ��

�� Anomaly h e t o m d �� m d �� o e h data t �� h t e t h e o o m d m �� d m d d m o o e h e t h data t h �� t �� e o m d d m o e h t h e t �� o m d �� m d o e �� h data t h t �� e �� o m d �� d m o e �� h t �� 18 �� 18 ��

�� e t h �� o m d �� d m o e �� h data t h t e o m d �� d m o h e t �� e t h �� e t h o o m m d d d m d m �� o o e e h h data t data t �� h h t t e e o o m m �� d d �� d d m m o o h e h e t t �� e t h �� o m d �� d m o e �� h data t h t �� e �� o �� m d �� d m o �� h e t �� e t h �� o m d �� d m �� o e �� h data t �� h t e �� o m �� d �� d m o h e t �� 19 �� 19 ��

�� e t h �� o m d �� d m o e �� h data t h t e o m d �� d m o h e t �� e t h �� e t h o o m m d d d m d m �� o o e e h h data t data t �� h h t t e e o o m m �� d d �� d d m m o o h e h e t t �� e t h �� o m d e t h �� o m d �� d m o �� e d m h data t o e h �� t �� h e data t o h m t �� d e �� o �� m d �� d m o �� h e t d m o �� h e t �� e t h �� o m d �� d m �� o �� e �� h data t �� h t �� e �� o m �� d �� d �� m o h e t �� 19 �� 19 ��

�� Active Object + �� State Machine mailbox t h e o m d m d o e h data t h t e o m d d m o e h t 20 �� 20 ��

�� Active Object + �� State Machine mailbox t h e o m d m d o e h data t h t e o m d d m o e h t 21 �� 21 ��

box empty full(X) 22 22

box empty {‘put’,X} full(X) 22 22

box empty {‘take’,From} / {‘put’,X} send(From, X) full(X) 22 22

box() ➞ empty(). empty() ➞ box receive {‘put’, X} ➞ full(X) end . empty {‘take’,From} / full(X) ➞ {‘put’,X} send(From, X) receive {‘take’, From} ➞ full(X) From ! X, empty() end . 23 23

box() ➞ empty(). empty() ➞ box receive {‘put’, X} ➞ full(X) end . empty {‘take’,From} / full(X) ➞ {‘put’,X} send(From, X) receive {‘take’, From} ➞ full(X) From ! X, empty() end . {‘peek’,From} / send(From,{‘ok’, X}) 24 24

box() ➞ empty(). empty() ➞ box receive {‘put’, X} ➞ full(X) end . empty {‘take’,From} / full(X) ➞ {‘put’,X} send(From, X) receive {‘take’, From} ➞ full(X) From ! X, empty(); {‘peek’, From} ➞ {‘peek’,From} / send(From,{‘ok’, X}) From ! {‘ok’, X}, full(X) end . 25 25

box() ➞ empty(). empty() ➞ receive {‘put’, X} ➞ full(X) end. full(X) ➞ receive {‘take’, From} ➞ From ! X, empty(); {‘peek’, From} ➞ From ! {‘ok’, X}, full(X) end. 26 26

box() ➞ empty(). Box = spawn(fun box/0), empty() ➞ receive {‘put’, X} ➞ full(X) end. full(X) ➞ receive {‘take’, From} ➞ From ! X, empty(); {‘peek’, From} ➞ From ! {‘ok’, X}, full(X) end. 26 26

box() ➞ empty(). Box = spawn(fun box/0), empty() ➞ Box ! {‘put’, 27}, receive {‘put’, X} ➞ full(X) end. full(X) ➞ receive {‘take’, From} ➞ From ! X, empty(); {‘peek’, From} ➞ From ! {‘ok’, X}, full(X) end. 26 26

box() ➞ empty(). Box = spawn(fun box/0), empty() ➞ Box ! {‘put’, 27}, receive {‘put’, X} ➞ Box ! {‘take’, self()}, full(X) receive end. Value ➞ print(Value) end full(X) ➞ receive {‘take’, From} ➞ From ! X, empty(); {‘peek’, From} ➞ From ! {‘ok’, X}, full(X) end. 26 26

Interface Objects Fixed API Protocol Actors API changes with internal state 27 27

Anomaly Interface Objects Fixed API Protocol Actors API changes with internal state 27 27

... each Smalltalk object is a recursion on the entire possibilities of the computer. Thus its semantics are a bit like having thousands and thousands of computers all hooked together by a very fast network. Alan Kay, Early History of Smalltalk 28 28

Just a gentle reminder ... Smalltalk is NOT only its syntax or the class library, it is not even about classes. I'm sorry that I long ago coined the term "objects" for this topic because it gets many people to focus on the lesser idea. The big idea is "messaging" -- that is what the kernel of Smalltalk/Squeak is all about... Alan Kay, October 1998 28 28

But isn’t this expensive? 29 29

But isn’t this expensive? ... heard in the ‘90s Use Objects! 29 29

But isn’t this expensive? ... heard in the ‘90s 100.000’s of objects, Use Objects! are you crazy? 29 29

But isn’t this expensive? ... heard yesterday 100.000’s of processes, Use Actors! silly you! 29 29

“What if the OOP parts of other languages (Java, C++, Ruby, etc.) had the same behavior as their concurrency support? What if you were limited to only creating 500 objects total for an application because any more would make the app unstable and almost certainly crash it in hard-to-debug ways? What if these objects behaved differently on different platforms?” Joe Armstrong, creator of Erlang as quoted in http://weblog.hypotheticalabs.com/?p=217 30

�� Effect Containment �� e t h o m d ■ Functional languages m d o e disallow effects h data t h t e o m d ■ Many object-oriented d m o styles encourage side e h t effects . ■ Actors confine effects �� 31 31 ��

From C++ to Java Garbage Collection State Containment From Java to Erlang 32 32

Threads and Locks don’t compose well ■ Threaded programs are error prone (we already knew that). ■ Good thread design requires global knowledge. 33 33

Threads and Locks don’t compose well ■ Threaded programs are error prone (we already knew that). ■ Good thread design requires global Anomaly knowledge. 33 33

�� Activity Composition �� spawn e t h e t h o o m m d d d m d m o o e e h h data t data t h h t t e e o o m m d d d d m m o o h e h e t t �� 34 �� 34 ��

�� Activity Composition �� link e t h e t h o o m m d d d m d m o o e e h h data t data t h h t t e e o o m m d d d d m m o o h e h e t t �� 35 �� 35 ��

�� Activity Composition �� link e t h e t h o o m m d d d m d m o o e e h h data t data t h h t t e e o o m m d d host d d host m m o o h e h e t t �� 35 �� 35 ��

“Let it Fail” philosophy e t h o m d m d o e h data t h t e o m d d m o e h t 36 36

“Let it Fail” philosophy e t h o m d ■ Write code with lots of assertions m d o e h data t h t e o m d d m o e h t 36 36

“Let it Fail” philosophy e t h o m d ■ Write code with lots of assertions m d o e ■ Let a meta-level do fault handling h data t h t e o m d d m o e h t 36 36

“Let it Fail” philosophy e t h o m d ■ Write code with lots of assertions m d o e ■ Let a meta-level do fault handling h data t h t e o m d ■ Defensive code is a symptom of a d m o e h t weak platform (segfaults, memory leaks, ...) 36 36

“Let it Fail” philosophy e t h o m d ■ Write code with lots of assertions m d o e ■ Let a meta-level do fault handling h data t h t e o m d ■ Defensive code is a symptom of a d m o e h t weak platform (segfaults, memory Anomaly leaks, ...) 36 36

Martin Fowler’s First Law of Distributed Objects Design rpc Starbucks doesn’t use transactions Steve Vinoski: RPC and its Offspring: Convenient, Yet Fundamentally Flawed 37 37

Martin Fowler’s First Law of Distributed Objects Design rpc Anomaly Starbucks doesn’t use transactions Steve Vinoski: RPC and its Offspring: Convenient, Yet Fundamentally Flawed 37 37

Abstractions 38 38

Abstractions ■ Any abstraction (hiding code) is problematic to distribute, persist, etc. 38 38

Abstractions ■ Any abstraction (hiding code) is problematic to distribute, persist, etc. ■ You want to distribute/persist simple data (as in sql databases, document stores) 38 38

Abstractions ■ Any abstraction (hiding code) is problematic to distribute, persist, etc. ■ You want to distribute/persist simple data (as in sql databases, document stores) ■ JSON’s popularity is a testament to this anomaly. 38 38

Abstractions ■ Any abstraction (hiding code) is problematic to distribute, persist, etc. ■ You want to distribute/persist simple data (as in sql databases, document stores) ■ JSON’s popularity is a testament Anomaly to this anomaly. 38 38

Simple Values 39 39

Simple Values ■ Tuple, List, Record, Number, String, Binary 39 39

Simple Values ■ Tuple, List, Record, Number, String, Binary ■ Pattern matching is polymorphism for values 39 39

Simple Values ■ Tuple, List, Record, Number, String, Binary ■ Pattern matching is polymorphism for values ■ Erlang data stores (like Mnesia) just store values, not bytes or objects. 39 39

Simple Values ■ Tuple, List, Record, Number, String, Binary ■ Pattern matching is polymorphism for values ■ Erlang data stores (like Mnesia) just store values, not bytes or objects. ■ Too much of my Java programs are boilerplate code. 39 39

“Object” Model Anomalies ■ Thread & Locks ■ Interfaces with Fixed API ■ Defensive Code ■ RPC/RMI ■ Boilerplate code for persistence 40 40

Actor “Solutions” ■ Processes w/ state containment ■ Protocols ■ Let it Fail ■ Async Messaging ■ Send & store simple Data 41 41

Making reliable distributed control systems in the presence of errors 43 43

Making reliable distributed control systems in the presence of errors ■ The “secret weapon” for Ericsson’s market leading, real-time telephony systems. 43 43

Making reliable distributed control systems in the presence of errors ■ The “secret weapon” for Ericsson’s market leading, real-time telephony systems. ■ 20+ years of experience to learn from. 43 43

Objects, Anomalies, and Actors: The Next Revolution Steve Vinoski - PowerPoint PPT Presentation

Objects, Anomalies, and Actors: The Next Revolution Steve Vinoski Architect, Basho Technologies QCon San Francisco 2011 18 Nov 2011 @stevevinoski http://steve.vinoski.net/ vinoski@ieee.org 1 This is actually Kresten Krab Thorups

Recently, several industries have experienced their digital revolution... Industry: Digital

5. Revolution and Napoleonic Europe 5.1 The Revolution in France 5.2 The Revolution and Europe

The Digital Revolution 1 Digital Revolution Nadias Theme 2 Digital Revolution Digital

Triple Revolution 1. Internet Revolution 2. Mobile Revolution 3. Social Media Revolution

Mining Anomalies Andrzej Wasylkowski 1 Why Mine Anomalies? How can we make programs more

Towards Type-safe Composition of Actors Dominik Charousset, January 2016 1 Problem Statement

1 7 8 ARL Robot Sense Plan Move Goal 9 10 Sense Plan Move Motion Learn library 11

1 The Second Industrial Revolution (cont.) In the Second Industrial Revolution there was

Actors in the ACE Architecture draft-ietf-ace-actors-02 Stefanie Gerdes, Ludwig Seitz, Goeran

Contents 1. Actors 2. Principles 3. Method 4. In a few words 2 1. Actors GRUNDTVIG

Actors Actors High Speed Rail Connec5on Minister

b s b c anomalies anomalies Found by LHCb (and perhaps Found by several experiments

61A Lecture 12 Announcements Objects (Demo) Objects 4 Objects Objects represent

What is Anomalies? If Efficient Market Hypothesis holds, all securities should have the same

Mutable Values Announcements Objects (Demo) Objects 4 Objects Objects represent

Virtual Actors Machine emulation of character gesture behaviour as portrayed by human actors - By

Tasks for Actors Frank S. de Boer Main Problem Modeling and analysis of real-time distributed

DDoS: Barbarians At The Gate(way) Examination of actors, tools and defenses #whoami Dave Lewis

Sons of the Sons of the American Revolution American Revolution JROTC/ ROTC & Service

Fast and Scalable Method for Resolving Anomalies in Firewall Policies Hassan Gobjua

61A Lecture 12 Announcements Objects (Demo) Objects Objects represent information They

Objects & Inheritance Section 7 Implementing Objects in 401 Ways of implementing objects:

Transforming Objects Ray : R(t) = s + c t Objects : Sphere, box, cone etc. We assume the objects

Flavour anomalies at the LHC M. Nardecchia INFN & Sapienza University of Rome 30 May 2019,

Objects, Anomalies, and Actors: The Next Revolution Steve Vinoski - PowerPoint PPT Presentation

Objects, Anomalies, and Actors: The Next Revolution Steve Vinoski Architect, Basho Technologies QCon San Francisco 2011 18 Nov 2011 @stevevinoski http://steve.vinoski.net/ vinoski@ieee.org 1 This is actually Kresten Krab Thorups

Recently, several industries have experienced their digital revolution... Industry: Digital

5. Revolution and Napoleonic Europe 5.1 The Revolution in France 5.2 The Revolution and Europe

The Digital Revolution 1 Digital Revolution Nadias Theme 2 Digital Revolution Digital

Triple Revolution 1. Internet Revolution 2. Mobile Revolution 3. Social Media Revolution

Mining Anomalies Andrzej Wasylkowski 1 Why Mine Anomalies? How can we make programs more

Towards Type-safe Composition of Actors Dominik Charousset, January 2016 1 Problem Statement

1 7 8 ARL Robot Sense Plan Move Goal 9 10 Sense Plan Move Motion Learn library 11

1 The Second Industrial Revolution (cont.) In the Second Industrial Revolution there was

Actors in the ACE Architecture draft-ietf-ace-actors-02 Stefanie Gerdes, Ludwig Seitz, Goeran

Contents 1. Actors 2. Principles 3. Method 4. In a few words 2 1. Actors GRUNDTVIG

Actors Actors High Speed Rail Connec5on Minister

b s b c anomalies anomalies Found by LHCb (and perhaps Found by several experiments

61A Lecture 12 Announcements Objects (Demo) Objects 4 Objects Objects represent

What is Anomalies? If Efficient Market Hypothesis holds, all securities should have the same

Mutable Values Announcements Objects (Demo) Objects 4 Objects Objects represent

Virtual Actors Machine emulation of character gesture behaviour as portrayed by human actors - By

Tasks for Actors Frank S. de Boer Main Problem Modeling and analysis of real-time distributed

DDoS: Barbarians At The Gate(way) Examination of actors, tools and defenses #whoami Dave Lewis

Sons of the Sons of the American Revolution American Revolution JROTC/ ROTC &amp; Service

Fast and Scalable Method for Resolving Anomalies in Firewall Policies Hassan Gobjua

61A Lecture 12 Announcements Objects (Demo) Objects Objects represent information They

Objects &amp; Inheritance Section 7 Implementing Objects in 401 Ways of implementing objects:

Transforming Objects Ray : R(t) = s + c t Objects : Sphere, box, cone etc. We assume the objects

Flavour anomalies at the LHC M. Nardecchia INFN &amp; Sapienza University of Rome 30 May 2019,

Sons of the Sons of the American Revolution American Revolution JROTC/ ROTC & Service

Objects & Inheritance Section 7 Implementing Objects in 401 Ways of implementing objects:

Flavour anomalies at the LHC M. Nardecchia INFN & Sapienza University of Rome 30 May 2019,