Fire-and-Forget: The unification of single-threaded, multi-threaded and asynchronous programming technology

Learning Resources Tutorials & Guides
3

@aisamu:
I am happy to know that the Warehouse/Workshop Model also achieves the unification of the distributed architecture.

I have always been an amateur personal PC developer. I do n’t understand the knowledge of distributed, streaming, and Flink. Through article via your link, I get the following points:

  • Flink Stateful Functions is more like my previous article Everything is RMDB.

  • In the Warehouse/Workshop Model, There is strictly no interaction between each workshop, and the “Flink Stateful Functions” diagram seems to be interactive. From this perspective, Flink Stateful Functions only defines the warehouse, and does not strictly define the workshop. It is a state server, which is more similar to ring web server. My previous article: Ring is also a Warehouse/Workshop Model

  • In the Warehouse/Workshop Model, the vast majority of the workshops are pipeline-function (pure function) or long-pipeline-function consisting of serially connected pipes. If not, then the side effect is at the end of the series of pipeline, similar to that, consumables such as office supplies or lubricants are sent from the warehouse to the workshop and are consumed.

  • Finally, I think it would be better and simpler if Flink Stateful Functions adhered to the Warehouse/Workshop Model more strictly.