Difference between revisions of "Message Bus"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
When someone needs an exploitation process to operate on a file, they put a message onto that process' queue. | When someone needs an exploitation process to operate on a file, they put a message onto that process' queue. | ||
When that process is ready to process data, it pulls a message from its queue. | When that process is ready to process data, it pulls a message from its queue. | ||
| + | |||
| + | =Truxton's Message Bus= | ||
| + | Messaging functionality in Truxton is implemented as a [[Message Bus Drivers|plugin]] to allow the use of different messaging technologies. | ||
| + | However, Truxton uses a database to host the message queues. | ||
| + | The name of the message queue is the name of the table in the database that contains the [[Message Bus Messages|messages]]. | ||
Latest revision as of 17:07, 7 July 2022
The way that Truxton can scale exploitation processing is by using a Message Bus.
What is a Message Bus
A message bus is way of using messages to communicate between processes. The messages reside in a message queue. Each Truxton exploitation process in the ETL layer subscribes to a message queue. When someone needs an exploitation process to operate on a file, they put a message onto that process' queue. When that process is ready to process data, it pulls a message from its queue.
Truxton's Message Bus
Messaging functionality in Truxton is implemented as a plugin to allow the use of different messaging technologies. However, Truxton uses a database to host the message queues. The name of the message queue is the name of the table in the database that contains the messages.
