flâneur

publications/IntroductionToSoftwareArchitectureWithActors/Part1/README.md at main · denyspoltorak/publications

github.com · 6,454 words · saved by 1 readers

Actors have been known for quite a while (1973) and have seen wide use in real-time (embedded, telecom, and gamedev) systems. Moreover, modern event-driven architectures fit the definition of actor systems, indicating that actors appear to have been (recently) reinvented. It even seems that OOP was originally defined through objects interacting via events, which made these early objects behave like actors. With the wider industrial adaptation of objects, people found that it was far easier to write business logic as a series of synchronous method calls rather than use message passing, redefining the concept of an object and forgetting about actors until distributed systems became mainstream. The modern literature on distributed architectures deals with testing pyramids, fault tolerance, and the selection of middleware and databases, as well as other important nuances of practicality. However, the very basic idea that the structure of a system defines its properties and applicability wa

Part 1 2 3 4 5 Introduction to Software Architecture with Actors: Part 1 – On Complexity Actors have been known for quite a while ( 1973 ) and have seen wide use in real-time (embedded, telecom, and gamedev) systems. Moreover, modern event-driven architectures fit the definition of actor systems, indicating that actors appear to have been (recently) reinvented. It even seems that OOP was originally defined through objects interacting via events , which made these early objects behave like actors. With the wider industrial adaptation of objects, people found that it was far easier to write busi

related reading