tl;dr Message-Passing Interfaces are ...
Some questions arise out of this:
A Message-Passing Interface tends to lead to several consequences:
A couple of different takes on the Message-Passing Interface include:
Architecturally, when components use messages to signal that particular criteria have been met or that state has changed, we call that an Event-Driven Architecture.
Fowler's Parameter Object (PEAA, ###) suggests taking the parameters to a method and putting them into a single object and passing that object as the sole parameter; if this is generalized across all the methods, and the method name is included as part of the object, we have essentially created a Message-Passing Interface.
Last updated: 10 March 2022Tags: pattern structural architectural