Moreover, the subdomains along the axis may vary (belong to different domains) at different heights (abstraction levels) for example, at the lower (OS) level, there is network, HDD, video, sound, mouse and keyboard drivers/interfaces, while the upper application level may be concerned with players, monsters and spells, and on top of it resides yet another layer with metadata: game scores, achievements, player rooms, etc. The horizontal axis resolves subdomains in an arbitrary order.The upper modules rely on the lower ones. Users pay for the higher levels of the software and don’t care about the low-level implementation unless something there goes wrong. The vertical axis maps abstraction – upper parts are more abstract (high-level business logic in Python or DSL), whereas lower parts are implementation-specific (device drivers in C or highly optimized library data structures).The following coordinates, abbreviated as ASS, will be used consistently: The remaining parts of the publication examine the relation between structural diagrams (drawings of components and their interactions) for common types of systems of actors/services and the properties of those systems. Nanoservices (Event-Driven Architecture).Load Balancer, aka Dispatcher (external dispatch).Leader/Followers (self-managing instances).Introduction to Software Architecture with Actors: Part 3 – On Simple SystemsĪfter having looked into the ways events are processed inside individual actors, it is time to try combining several actors (or splitting an actor by messaging interfaces).
0 Comments
Leave a Reply. |