What elements are needed to implement a remote event-driven system? - review required

I am trying to create an event-driven system in which system elements interact to generate events that other components of the system respond to. The components are supposed to be independent of each other - or pretty much independent of how I can make them. First, the system will be implemented in Windows 7 and will be written in Delphi. The generated events will be generated by Delphi code. I understand how to implement the type system described on one machine.

I want to create a system so that it can be easily deployed on different machine architectures, in particular, with various components working on a distributed architecture, which may be different for Windows 7. Require that the system never communicates with any external systems.

I tried to study the architecture that I need to consider, and examined the issues mentioned below. They seem to indicate the use of named pipes as an interservice communication mechanism. As a result of these studies, I sketched the following to describe my system: the first part of the diagram is the system that I am developing it; the second part, which I deduced, I will need for possible future implementations. Design sketch

This leads to the following points:

  • Can you send events through named pipes?
  • ?
  • ?
  • ( )?

? Delphi ?

EDIT:

, "@I ", . :

  • v -
  • FIFO.
  • - - .
  • - ( ) - .
+3
4

( ) , Java. . Delphi , - .

, / Delphi.

:

" " , .


, Delphi , xmlBlaster, RabbitMQ, Amazon Simple Queue Service , .

+3

4 : , . , , . ? ? FIFO. , (- )?

, , , ?

. , , . , .

, , . FIFO ? ? ?


- , . Erlang , , (, , , ).

+2

RabbitMQ, http://www.rabbitmq.com/. . delphi, -.

+1

This is probably just a message queue application.

http://msdn.microsoft.com/en-us/library/ms632590(v=vs.85).aspx

0
source

Source: https://habr.com/ru/post/1788080/


All Articles