(@FolMing), Zakhar (@onelxj), and Artur (@ArthurBandaryk) ## chapters (1) motivating futures/promises + actors (2) libprocess (3) revisiting the problem (4) evolution of libprocess (5) eventuals (6) scheduling scheduling (7) streams (8) type erasure ## chapters (1) motivating futures/promises + actors (2) libprocess (3) revisiting the problem (4) evolution of libprocess (5) eventuals (6) scheduling (7) semaphores 1973: actors 1974: monitors 1978: communicating sequential processes (CSP) 1987: statecharts ## possible solutions with threads 1963: mutexes, semaphores 1973: actors 1974: monitors 1978:

bacon_number(size(actors)); for (auto&&[u, v] : bfs_edge_range(costars, 1)) { bacon_number[v] = bacon_number[u] + 1; } for (int i = 0; i < size(actors); ++i) { std::cout << actors[i] << relationships between actors forms a graph • A BFS of that graph gives each actor a “Bacon number” • Unfortunately, the co-star graph doesn’t actually exist • IMDB: • Movies table • Actors table • Movies-Actor bacon_number(size(actors)); for (auto&&[u, v] : bfs_edge_range(costars, 1)) { bacon_number[v] = bacon_number[u] + 1; } for (int i = 0; i < size(actors); ++i) { std::cout

} ) The following query finds and populates a list of domain objects: ## Java List actors = this.jdbcTemplate.query( "select first_name, last_name from t_actor", (resultSet 中国大陆名); actor.setLastName(resultSet.中国大陆名); return actor; }); ## Kotlin val actors = jdbcTemplate.query("select first_name, last_name from t_actor") { rs, _ -> Actor(rs jdbcTemplate.update( "call SUPPORT.REFRESH_ACTORS_SUMMARY(?)", Long.valueOf(unionId)); Kotlin jdbcTemplate.update( "call SUPPORT.REFRESH_ACTORS_SUMMARY(?)", unionId.toLong()) More sophisticated

have "Bill" in the name select * from movie where name like '%Bill%'; -- Find all actors and their roles who played in a movie -- with "Bill" in the name select fname, lname, role (') instead of (\') as in MySQL -- Table structure for table `actors` DROP TABLE IF EXISTS `actors`; CREATE TABLE `actors` ( `id` int(11) NOT NULL default '0', `first_name` varchar(100) PRIMARY KEY (`id`) ); -- Dumping data for table `actors` INSERT INTO `actors` VALUES (933, 'Lewis', 'Abernathy', 'M'); insert into `actors` values (2547, 'Andrew', 'Adamson'

Enterprise Developers Being asked to develop resilient, scalable, microservice-based apps Functions and Actors are powerful programming models They write in many languages They want to leverage existing code _2.jpg) dapr API State management Publish and subscribe Resource bindings & triggers Actors Distributed tracing Extensible... ## Dapr: Build apps using any language with any framework Any Service-to-service invocation State management Publish and subscribe Resource bindings & triggers Actors Distributed tracing ![Image](/uploads/documents/7/8/e/d/78edb81a9976122a3d4c851701bf9145/p28_1

Communication? • Abstraction: channels... or actors Two main cases in practice • concurrent queues • networking sockets ## Communication? • Abstraction: channels... or actors Two main cases in practice • concurrent MPMC, MPSC, SPMC, SPSC, Lockfree, Blocking... ## Communication? • Abstraction: channels... or actors Two main cases in practice • concurrent queues Bounded/Unbounded, Sync/Async, MPMC, MPSC, SPMC /f/8c2fd06048f22f2c26c8dd372dcf93bf/p53_1.jpg) ## Communication? • Abstraction: channels... or actors Two main cases in practice • concurrent queues • networking sockets io_context, resolver, acceptor

a topic to receive messages.| |4|Bindings|A bi-directional connection to an external service.| |5|Actors|An independent unit of computation.| |6|Observability|A series of components for logging, tracing https://github.com/dapr/dapr/blob/5aba3c9aa4ea9b3f388df125f9c66495b43c5c9e/pkg/http/api.go ## Threat actors A threat actor is an individual or group that intentionally attempts to exploit vulnerabilities sabotage. We identify the following threat actors below; For example, a fully untrusted user can also be a contributor to a 3rd-party library used by Dapr. actors for Dapr. A threat actor can assume multiple

We then cover how it interacts with the internal components of Vitess. Next, we specify the threat actors that could have a harmful impact on a VTA_{admin} deployment. Finally we exemplify several threat scenarios based on the observations we made when outlining the core components and the specified threat actors. We used the following sources for the threat modelling: - Vitess’s documentation including README aligned, but they are also different. Other components of Vitess have different attack vectors, threat actors and security designs. The threat model in this report is solely for Vitess's VTA_{Admin} component

microservice-based apps They write in many languages They want to leverage existing code Functions and Actors are powerful programming models ## What is holding back micro-service development? ![Image](/up invocation 0 State management 三 Publish and subscribe C Resource bindings and triggers 🌸 Actors 🌐 Distributed tracing X Extensible ![Image](/uploads/documents/b/c/2/9/bc29b5fbf1de02f8968a900b84d384e5/p30_1 large array of inputs Output bindings to external resources including databases and queues 🌸 Actors Encapsulate code and data in reusable actor objects as a common microservices design pattern ⚽️

associate certificate holders with organization R4. NC4 can then use this MSP name in policies to grant actors from R4 particular rights over network resources. An example of such a policy is to identify the apply for channel configurations with respect to peers. In our network, P1 and P2 are likewise good actors. When peer nodes P1 and P2 are interacting with client applications A1 or A2 they are each using We’ll see later the same pattern for actors in channel and its channel configuration CC2. Again, we can see that while the peers and applications are critical actors in the network, their behaviour in a